aa-panel

aa-panel is a skill for Claude Code from Peeyushmeher/agent-agile. It costs 40 tokens per session (682 once invoked), scanned A, original, MIT.

An adversarial review panel for checking a drafted multi-epic project plan before implementation. It uses separate critics to examine the product idea, specification, and execution plan.

In plain words
What is it for?
Use it to review project and roadmap files, inspect story cards and contracts, and decide what must be fixed before execution.
Why use it?
It finds missing requirements, unclear details, and likely collisions or delays while the plan is still easy to change.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: reads .claude/ paths; mentions subagents.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the agent-agile plugin — 11 skills, 11 agents shipped together

Good fit Use it to review project and roadmap files, inspect story cards and contracts, and decide what must be fixed before execution.

Compare 6 skills from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add Peeyushmeher/agent-agile
Claude Code
/plugin install agent-agile

Made for: Claude Code.

Or install agent-agile, the plugin that ships this one along with the rest of its 11 skills, 11 agents.

Wrote 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.

agentmods badge for aa-panel

README.md
[![agentmods](https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-panel/github.svg)](https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-panel)
Your own site
<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.

agentmods 80×15 button for aa-panel

Your own site · 80×15
<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>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 682 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 10d ago against content hash 417cfec75162, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

skills/aa-panel/SKILL.md · 25 lines

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

  1. 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.md if it exists, and .planning/RESEARCH.md if it exists (per Panel protocol, the spec auditor alone receives it).
  2. Read .planning/CONFIG.md for the smart_tier and commercial fields.
  3. Spawn aa-critic-product, aa-critic-spec, and aa-critic-execution as parallel fresh subagents, each with the model configured for its tier in .planning/CONFIG.md. If commercial: yes, also spawn aa-critic-market the same way. Give each subagent exactly two inputs: its two sections of playbooks/critics.md verbatim — Panel protocol plus 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.
  4. Collect every subagent's Verdict format block.
  5. Fix every BLOCK finding by invoking planner behavior per playbooks/planner.md — spawn a fresh aa-planner subagent 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.
  6. Present the remaining FLAG findings plus the fixed plan to the user; the user's decision is the gate.
  7. 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.md from playbooks/templates/LEARNINGS.md explaining why, and stop.
  8. Update .planning/STATE.md to record the outcome of the gate.

Read the full file on GitHub · 25 lines

Changes

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.

  1. 10d ago First seen · 25 lines · 40 tokens per session scan A 417cfec75162

Subscribe to this mod's changes

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.

Related

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.

buiphucminhtam/forgewright · 68 tokens

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.

yonatangross/orchestkit · 61 tokens

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.

Adelie-Squad/solosquad · 39 tokens

workflow-refinement

A post-workflow review process that examines how stages depend on one another and how information is handed between them.

Adelie-Squad/solosquad · 35 tokens

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.

jeffreytse/grimoire-core · 50 tokens

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.

borghei/Claude-Skills · 45 tokens