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/skills/peeyushmeher/agent-agile/aa-panel)<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-panel"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-panel/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/skills/peeyushmeher/agent-agile/aa-panel"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-panel.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.00682 |
| Opus 5 | $0.00020 | $0.00341 |
| Sonnet 5 | $0.00008 | $0.00136 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
aa-panel 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.
How it starts
The opening of the file, as written. The whole thing — 25 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aa-panel
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 in full — Panel protocol, Product critic, Spec auditor, Execution auditor, Market critic, Verdict format — and follow it exactly; do not re-derive or improvise the panel's doctrine. The panel gate in Panel protocol applies here: run this skill only for multi-epic projects — a single-epic throwaway skips the panel entirely.
Wiring
- Read the draft plan:
.planning/PROJECT.md,.planning/ROADMAP.md, the current epic's story cards at.planning/epics/EPIC-NN/stories/S*.md,.planning/epics/EPIC-NN/CONTRACTS.mdif it exists, and.planning/RESEARCH.mdif it exists (per Panel protocol, the spec auditor alone receives it). - Read
.planning/CONFIG.mdfor thesmart_tierandcommercialfields. - Spawn
aa-critic-product,aa-critic-spec, andaa-critic-executionas parallel fresh subagents, each with the model configured for its tier in.planning/CONFIG.md. Ifcommercial: yes, also spawnaa-critic-marketthe same way. Give each subagent exactly two inputs: its two sections ofplaybooks/critics.mdverbatim —Panel protocolplus its own critic section (the same pair its agent definition names) — and the full draft plan gathered in step 1; nothing else. They do not see each other's output. - Collect every subagent's Verdict format block.
- Fix every
BLOCKfinding by invoking planner behavior perplaybooks/planner.md— spawn a freshaa-plannersubagent with the model configured for the smart tier in.planning/CONFIG.md, or apply the fix inline in the main loop if already holding full planning context; inline is default. Only the critic(s) whose findings forced a structural change get re-run, and only once. - Present the remaining
FLAGfindings plus the fixed plan to the user; the user's decision is the gate. - If the market critic's verdict is
KILL, present its evidence and recommend stopping instead of presenting the plan for approval. If the user agrees to stop, write.planning/epics/EPIC-NN/LEARNINGS.mdfromplaybooks/templates/LEARNINGS.mdexplaining why, and stop. - Update
.planning/STATE.mdto record the outcome of the gate.
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 · 25 lines · 40 tokens per session scan A 417cfec75162
aa-panel is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 682 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 skills, from other repositories
project-manager
This skill has been upgraded with agentic AI capabilities, OKR/KPI integration patterns, and async-first workflows based on 2026 PM best practices research.
product-frameworks
Product management frameworks for business cases, market analysis, strategy, prioritization, OKRs/KPIs, personas, requirements, and user research. Use when building ROI projections, competitive analysis, RICE scoring, OKR trees, user personas, PRDs, or usability testing plans.
skill-refinement
A review tool for measuring how well other skills work over time. It examines task records, unresolved questions, costs, failures, repeated work, and changes in confidence.
workflow-refinement
A post-workflow review process that examines how stages depend on one another and how information is handed between them.
run-team-retrospective
Use when a team needs to reflect on a completed period, project, or significant event — to extract what worked, what didn't, and what specific changes to make before the next cycle, rather than repeating the same patterns.
free-tool-strategy
Free tool marketing strategy covering idea evaluation, tool design, lead capture architecture, SEO landing pages, launch playbook, and ROI measurement for calculators, generators, checkers, graders, and interactive tools.