shiehn

DeclarAgent: Run Auditable Workflows for AI Agents

DeclarAgent runs YAML-defined workflows through shell commands, built-in actions, and HTTP requests. Its validation, dry-run, approval gates, and MCP integration suit teams that want agents to invoke controlled CLI workflows.

View on GitHub Compare
Stars
10
Forks
0
Stars, last 30 days
+0
Last commit
7 months ago
Contributors
1

Our take

Quietno commits in the last 90 days and no release in a year

Health score

16/100

How it is scored
Activity
19
Community
4
Issues
21
Pull requests
20

+0 stars in the last 30 days

  • Fewer contributors than 91% of the projects we track

DeclarAgent offers a clear, safety-oriented approach to agent-run workflows, but its quiet maintenance and single-contributor history make it a cautious choice for critical operations without independent review.

Good fit if

  • You want YAML-defined workflows that agents can discover and call through MCP.
  • Dry-runs and explicit approval for marked destructive steps match your execution controls.
  • Your team can review and maintain a Go CLI dependency under the MIT license.

Look elsewhere if

  • You need evidence of ongoing maintenance, since the project has had no commits in recent months and no release in the past year.
  • You require a project with a broader maintainer base; most of the code comes from one person.
  • Your adoption requires tests to be present in the repository; tests are not reported in the project facts.
All health signals
Last commit2026-03-07 (7 months ago)
Commits, last 90 days0
Releases, last 12 months0
Contributors1
Issues closed, last 90 days0
Pull requests merged, last 90 days0
Project age8 months

Checked on 2026-10-14 with the GitHub API.

Project history

Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.

Selected snapshot

Stars

10

Forks

0

Change since Nov 13, 2026: 0 stars·0 forks

Overview

DeclarAgent is a Go command-line tool for defining multi-step workflows in YAML and letting AI agents run them. It addresses the risk of agents executing ad hoc commands by making workflows inspectable and reusable before they run.

Plans can combine shell commands, built-in file and JSON actions, and HTTP requests. DeclarAgent can expose plans as tools through an MCP server, so it is aimed at teams that want agents to invoke approved workflows without needing to construct every command themselves.

Key Features

  • Validate plans and check their structure and references before execution.
  • Explain and dry-run plans to inspect resolved steps before making changes.
  • Require an explicit --approve flag for steps marked destructive.
  • Chain step outputs into later steps using templates.
  • Combine shell commands, HTTP requests, and built-in file, JSON, and environment actions.
  • Return structured JSON results and typed errors for automation and agent handling.
  • Expose plans as callable tools through MCP, or generate a Claude Code Skill.

Use Cases

  • Platform or DevOps teams: encode repeatable build or deployment steps in YAML and require approval for marked destructive actions.
  • Agent developers: let an LLM invoke a known workflow through MCP instead of assembling shell commands for each task.
  • Internal tooling teams: connect shell operations and HTTP APIs in one plan, with outputs passed between steps.
  • Teams prototyping agent workflows: validate and dry-run plans before enabling real execution.

What you need

Detected in the repository

  • Go 1.25.0 or newer (from go.mod)
  • Automated checks on GitHub Actions

License in plain words

MITpermissive

  • Commercial use: yes
  • Modify and redistribute: yes
  • You must keep: the copyright and license notice
  • Share your changes: no

A summary, not legal advice: the LICENSE file is what applies.

Getting Started

Install with Go, then validate a plan:

go install github.com/shiehn/declaragent@latest
declaragent validate plan.yaml

See the README for plan examples, CLI options, and MCP setup.

Considerations

The project is marked Quiet: it has had no commits in the last 90 days and no release in a year. It has one contributor, with work concentrated on that person, so teams should assess their capacity to review changes and handle issues. The project facts do not report tests, although the README documents a go test ./... command and CI. The README says macOS is the only platform currently tested; Linux is expected to work, while Windows requires WSL or a similar POSIX-compatible shell. The Go module specifies Go 1.25.0. Shell commands and HTTP requests can have real side effects, so approval gates and dry-runs should be part of a team's own operating procedure.

Found this useful?

Share it with someone who would like DeclarAgent.

Comparisons