Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Peeyushmeher/agent-agile --skill aa-statusgit clone --depth 1 https://github.com/Peeyushmeher/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-status)<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-status"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-status/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-status"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-status.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.00057 | $0.00424 |
| Opus 5 | $0.00028 | $0.00212 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00006 | $0.00042 |
Grade A, and why
aa-status 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.
What it actually says
aa-status
Read-only — never write to any file, never dispatch a subagent.
If .planning/STATE.md does not exist, say so and point the user at the three front doors: a vague spark → /aa-grill, a clear idea → /aa-new-project, an existing plan or spec → /aa-import.
Otherwise, render four sections in order, sourced from the files named:
- Roadmap. Read
.planning/ROADMAP.mdand reproduce its epic table as-is: number, epic name, demo sentence, initiative served, and status. - State. Read
.planning/STATE.mdand summarize its fields in plain language: which phase the project is in, what's in progress now, what's next, and any blocker. - Key Result progress. Read
.planning/PROJECT.md's Key Results list and restate each one. For any Key Result whose progress is evidenced elsewhere on disk — aLEARNINGS.mdnote, a verified epic whose demo sentence maps onto it — note that evidence next to it; otherwise mark it as not yet measured. Never invent a number that isn't backed by something on disk. - Outstanding prerequisites. Read
.planning/PREREQS.mdand list only the rows whose status is notverified(that is,pendingordone) — adonerow still belongs here, because "done" without "verified" means nobody has confirmed it actually works yet. If every row isverified, say so explicitly rather than showing an empty section.
Present all four sections together as one status report; don't ask the user which section they want first.
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 · 23 lines · 57 tokens per session scan A f441cb378c1f
aa-status is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 424 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.
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.