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-resume)<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-resume"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-resume/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-resume"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-resume.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.00061 | $0.00491 |
| Opus 5 | $0.00030 | $0.00246 |
| Sonnet 5 | $0.00012 | $0.00098 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
aa-resume 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
aa-resume
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/execution.md's "Resume protocol" section from that root, and follow it exactly:
- If
.planning/STATE.mddoes not exist, no project has been started here yet. Say so plainly, and point the user at the three front doors instead of guessing at a state that isn't there: a vague spark →/aa-grill, a clear idea →/aa-new-project, an existing plan or spec →/aa-import. - Otherwise, read
.planning/STATE.mdfirst and only. Don't re-derive status by re-reading the whole epic history —STATE.mdis the baton, kept small on purpose so this step stays cheap every time. - Follow its pointers — at most three files — and read exactly those, nothing wider.
- Continue the work from exactly where
STATE.mdsays the run is: the phase it names (grill, intake, panel, prereqs, an epic's wave, review, or done), the "Now" sentence, and the "Next" sentence. - If
STATE.mdnames a blocker, resolve or surface that blocker before doing anything else — never work around it silently.
Close the session, without exception, with one STATE.md update: what's in progress, what's next, the pointers the next session needs, and any blocker. A session that stops without this update leaves the next session to reconstruct state from scratch — the entire point of the baton is that this never has to happen.
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 · 22 lines · 61 tokens per session scan A 261d17c201a9
aa-resume is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 61 tokens to every session and 491 once invoked, about $0.0003 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.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
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…
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.