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-plan-epic)<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-plan-epic"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-plan-epic/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-plan-epic"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-plan-epic.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.00042 | $0.00973 |
| Opus 5 | $0.00021 | $0.00487 |
| Sonnet 5 | $0.00008 | $0.00195 |
| Haiku 4.5 | $0.00004 | $0.00097 |
Grade A, and why
aa-plan-epic 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aa-plan-epic
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/planner.md sections "Slicing epics into stories" and "The worker-readiness test", playbooks/system.md section "The memory spine", and playbooks/critics.md section "Panel refresh", and follow them exactly; do not re-derive or improvise the slicing process. When the epic is a UI epic (its demo sentence describes something a person sees or clicks), also read playbooks/design.md and apply it: design directions before Wave 0 on the first UI epic with no design system (2–4 self-contained HTML mockups, pick recorded in .planning/DECISIONS.md, tokens into the contracts), and a data-verify contract on every UI story card.
Wiring
- Read exactly three files — the three-file epic-to-epic read rule from "The memory spine":
.planning/PROJECT.md,.planning/ROADMAP.md, and the previous epic'sLEARNINGS.md. Read nothing else from prior epics, with the memory spine's two slicing-time exceptions: read.planning/DECISIONS.mdwhen it exists (settled decisions carry forward, never re-opened), and run one targeted grep across all prior epics'LEARNINGS.mdfor this epic's files and topics — a search, never a read-everything; bake any hits into the story cards. - Identify the next pending epic on the roadmap.
- Slice it into story cards per
playbooks/planner.md"Slicing epics into stories": enumerate every shared artifact, assign each one to Wave 0 or to exactly one story, pairwise-check every story's file list against every other story's in the same wave for overlap, and assign waves — Wave 0 (contracts and shared setup), Wave 1 (parallel stories with no cross-story reads), Wave 2 (integration, with an epic-level acceptance check tied to the demo sentence). - Write each story card to
.planning/epics/EPIC-NN/stories/S*.mdfromplaybooks/templates/STORY.md— one file per story, exactly the five fields: Goal, Files it owns, Acceptance check, Grader, Contracts consumed. Split a story only for parallel width or fresh-mind verification, perplaybooks/planner.md"Slicing epics into stories" — never because two things merely feel like separate concerns. - Run the worker-readiness test from
playbooks/planner.md"The worker-readiness test" against every card in the epic — no sampling. A card that fails gets split, sharpened, or has its ambiguity moved into Wave 0'sCONTRACTS.md. Do not report the epic sliced while any card still fails the test. - Panel refresh check. If
ROADMAP.mdholds 5 or more epics and the epic just sliced sits in the 4th, 7th, 10th … row position (current row order, re-derived now, never stored), run the panel refresh perplaybooks/critics.md"Panel refresh": read.planning/CONFIG.mdfor the smart tier (the deliberate, narrow exception to step 1's three-file rule), spawnaa-critic-specandaa-critic-executionas parallel fresh subagents with standard panel inputs, fix every BLOCK inline with the affected critic re-run once, and route FLAGs by gate mode as the playbook defines. A BLOCK still standing after the re-run stops an autopilot run with aSTATE.mdupdate, exactly like a circuit breaker. Run the KR-drift tripwire against theLEARNINGS.mdalready in hand from step 1. - Update
.planning/STATE.md: phase set to the new epic's wave, what's in progress, the next action, and pointers to the files the next session must read.
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 · 24 lines · 42 tokens per session scan A 6e2b04023a76
aa-plan-epic is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 973 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.
team-okrs
An OKR tracking page for a quarter. OKRs, or objectives and key results, are goals paired with measurable results.
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.
gr-product-dev-ops
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified…
derive-capacity
Work out how many points a week each person on the aeman board actually gets through, from the cards they have closed, and set it as their capacity after the lead confirms. Use when a team lead asks about throughput, weekly capacity, how much a person or a team can take, or wants the numbers over the columns filled in.
size-cards
Size the unsized cards of a team or a person on the aeman board — S/M/L/XL by a fixed rubric, written back through the aeman MCP after the lead confirms. Use when a team lead asks to estimate, size or weigh cards, or before a planning meeting.