Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bdfinst/agentic-dev-team/plugin install dev-teamWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/agents/bdfinst/agentic-dev-team/progress-guardian)<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/progress-guardian"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/progress-guardian/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/bdfinst/agentic-dev-team/progress-guardian"><img src="https://agentmods.dev/badge/agents/bdfinst/agentic-dev-team/progress-guardian.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.00913 |
| Opus 5.5 | $0.00008 | $0.00365 |
| Sonnet 5.5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00091 |
Grade A, and why
progress-guardian scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Progress Guardian
Cites:
- adversarial-review-protocol
- directory-enumeration Enforcement: script
Implemented by: ${CLAUDE_PLUGIN_ROOT}/scripts/progress_guardian.py
Output JSON: per ${CLAUDE_PLUGIN_ROOT}/knowledge/review-agent-output-contract.md (Whole-file load: short, canonical schema).
Status: pass=on track, warn=drift detected, fail=plan violation or scope creep Severity: error=skipped step or plan deviation, warning=uncommitted work accumulating, suggestion=consider committing Confidence: high=mechanical (step skipped, test missing); medium=judgment call (scope boundary); none=requires human input
Context needs: full-file (reads plan + git state)
Skip
Produces {"status": "skip", "issues": [], "summary": "No active plan found"} when:
- No plan files exist in
plans/or.claude/memory/— check withGlob("plans/**")/Glob(".claude/memory/**"), never a bareReadof the directory (${CLAUDE_PLUGIN_ROOT}/knowledge/directory-enumeration.md, Whole-file load: a short single-rule reference) - The current task has no associated plan
What the script detects
Plan adherence:
- Steps executed out of order without justification
- Steps skipped entirely
- Work done that doesn't map to any plan step
- Tests not written before implementation (RED before GREEN)
Commit discipline:
- A done (
[x]) step with no matching commit in git log - Large uncommitted change sets spanning multiple steps
- Commit messages that don't reference the plan step
Scope creep (--skip-llm path emits llm-skipped warning; LLM path assesses intent):
- Files changed that aren't declared in the plan (backtick-quoted paths)
- New functionality beyond plan scope
- Refactoring beyond what the current step specifies
Pre-PR gate (--pre-pr flag):
- Any
[ ]unchecked step blocks the PR - Uncommitted changes block the PR
- Declared-scope adherence (issue #865): out-of-scope edits against a slice's declared
**Files:**are a named warning, never a gate failure — freeze (opt-in via plan metadata) is the actual enforcement mechanism
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 80 lines · 21 tokens per session scan A 609b498eef78
progress-guardian is an agent published in the GitHub repository bdfinst/agentic-dev-team (295 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 913 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
committer
Agent that first generates the result report for a verified TASK and then performs git commit. Automatically invoked by the scheduler. Result files are created in the corresponding WORK directory.
Jira Workflow Steward
Expert delivery operations specialist who enforces Jira-linked Git workflows, traceable commits, structured pull requests, and release-safe branch strategy across software teams.
task-executor
Use this agent to execute a single tracked task with TDD, commit, and PR creation in an isolated git worktree. Dispatched by /coco:loop for parallel execution. Context: Multiple tasks are ready with non-overlapping file ownership. /coco:loop dispatches parallel agents. assistant: "I'll dispatch task-executor agents…
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
module-registrar
Register new modules in the Datacore ecosystem. Use this agent: When creating a new module for community contribution For :AI:module:register: tagged tasks To update CATALOG.md with new module entries To create GitHub repos and PRs for module registration Part of the community contribution workflow (DIP-0001).