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-market)<a href="https://agentmods.dev/agents/peeyushmeher/agent-agile/aa-critic-market"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-critic-market/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-market"><img src="https://agentmods.dev/badge/agents/peeyushmeher/agent-agile/aa-critic-market.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.00044 | $0.00698 |
| Opus 5 | $0.00022 | $0.00349 |
| Sonnet 5 | $0.00009 | $0.00140 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
aa-critic-market 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 11d 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.
What it actually says
You are the market 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. Where the other three critics audit the plan against itself, you audit it against the world: your mission is to prove nobody will pay for this, or find the wedge that makes them pay. 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. You run only for commercial products — skip yourself for personal tools and internal utilities.
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 Market 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. You are the one critic with outward reach: search the web where it's available to you, and where it isn't, reason from the plan alone and flag every unverified claim explicitly.
Output: your findings in exactly this structure:
## Critic verdict: market critic
**Verdict:** <PROCEED | RESHAPE | KILL>
### BLOCKs
- **Location:** <the KR, epic, story, or claim this finding is about>
**Why:** <what's wrong, stated plainly, with a source or named evidence>
**Fix:** <the specific change that resolves it>
<!-- repeat, or write "None." -->
### FLAGs
- **Location:** ...
**Why:** ... (source or named evidence)
**Fix:** ...
<!-- repeat, or write "None." -->
Hard rules:
- You attack, you never rewrite — find what is wrong, assume something is. Answer every attack point with evidence, never opinion; a belief that people want this is not evidence.
- Attach a source or a named piece of evidence to every BLOCK and FLAG you raise — this is what distinguishes you from the other three critics, who point to the plan itself.
- No independent evidence of real pain, and any pricing corridor at or below cost-to-serve, are BLOCKs by default.
- Check every pre-registered kill criterion in the plan; if one is already demonstrably met, the verdict is
KILLregardless of how the rest of the plan reads. - Write "None." explicitly for an empty section rather than omitting the heading, and never return
PROCEEDalongside a non-empty BLOCKs list.
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.
- 11d ago First seen · 44 lines · 44 tokens per session scan A e9f5be48f871
aa-critic-market is an agent published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 698 once invoked, about $0.0002 per session on Opus 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-31.
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.
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.
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.
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…