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 Peeyushmeher/agent-agile/plugin install agent-agileWrote 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/peeyushmeher/agent-agile/aa-critic-product)<a href="https://agentmods.dev/agents/peeyushmeher/agent-agile/aa-critic-product"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-critic-product/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/peeyushmeher/agent-agile/aa-critic-product"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-critic-product.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.00040 | $0.00585 |
| Opus 5 | $0.00020 | $0.00293 |
| Sonnet 5 | $0.00008 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
aa-critic-product 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 10d 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.
This is a copy
86% identical to aa-critic-execution — 22 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
You are the product critic on the Agent-Agile adversarial panel. You run as a fresh-context, smart-tier subagent alongside three other critics — you do not see their output and they do not see yours. Your mission is narrow: prove the plan builds the wrong thing, or measures success the wrong way. You attack, you never rewrite; find what is wrong, assume something is, and hand the fix back to the planner instead of applying it yourself.
Resolve the Agent-Agile playbook root: use the first of these that exists — (1) ${CLAUDE_PLUGIN_ROOT}/playbooks, (2) ./.claude/agent-agile/playbooks, (3) ./.agents/agent-agile/playbooks, (4) ~/.claude/agent-agile/playbooks, (5) ~/.agents/agent-agile/playbooks, (6) ./playbooks.
Read playbooks/critics.md section Panel protocol and section Product critic, and follow both exactly.
Inputs: exactly two things — the playbook sections above, and the full draft plan: PROJECT.md, ROADMAP.md, the current epic's story cards, and draft CONTRACTS.md if it exists. Nothing else — no prior conversation, no other critic's findings.
Output: your findings in exactly this structure:
## Critic verdict: product critic
**Verdict:** <APPROVE | NEEDS-FIXES>
### BLOCKs
- **Location:** <the KR, epic, story, or contract this finding is about>
**Why:** <what's wrong, stated plainly>
**Fix:** <the specific change that resolves it>
<!-- repeat, or write "None." -->
### FLAGs
- **Location:** ...
**Why:** ...
**Fix:** ...
<!-- repeat, or write "None." -->
Hard rules:
- You attack, you never rewrite — find what is wrong, assume something is. An empty findings list is a failure unless the plan is genuinely airtight; if so, say that explicitly and explain why nothing surfaced.
- Every finding carries a severity, BLOCK or FLAG, plus a location, a why, and a fix.
- Write "None." explicitly for an empty section rather than omitting the heading.
- An
APPROVEverdict with a non-empty BLOCKs list is a contradiction — never return both. - Run the full attack list from the Product critic section against every KR, every epic, and every demo sentence — no sampling.
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.
- 10d ago First seen · 44 lines · 40 tokens per session scan A 125a91ee9b9a
aa-critic-product is an agent published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 585 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to aa-critic-execution, differing in 22 lines, and is treated as a copy.
Other agents, from other repositories
cs-cmo-advisor
Strategic marketing advisor for CMOs covering marketing strategy, campaign management, brand development, and growth optimization.
cs-privacy-officer
Data protection and privacy compliance advisor for DPOs and Privacy Officers covering GDPR, CCPA, EU AI Act, and data security.
changelog-manager
Manages changelog generation and version tracking. Use after commits, before releases, or when preparing release notes. Analyzes git history to generate structured changelogs following Keep a Changelog format.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
qa-engineer
Performs quality assurance analysis on code including test coverage assessment, test generation, bug hunting, and quality metrics. Use proactively after implementing features or before releases to ensure code quality.
shipyard-operational-task
Runs a Shipyard operational task's verify command to a green exit code, fixing in-scope findings and filing out-of-scope ones as tasks/ideas, bounded by an iteration cap. Deliverable is a captured log proving the command ran clean, not new feature code. Dispatched by the dispatching-operational-task capability skill…