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-grill)<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-grill"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-grill/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-grill"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-grill.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.00045 | $0.00626 |
| Opus 5 | $0.00023 | $0.00313 |
| Sonnet 5 | $0.00009 | $0.00125 |
| Haiku 4.5 | $0.00005 | $0.00063 |
Grade A, and why
aa-grill 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.
How it starts
The opening of the file, as written. The whole thing — 28 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aa-grill
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 section The Grill in full, including the Grill → intake mapping table inside it, and follow it exactly — do NOT re-derive or improvise the system. The interrogation script, its handling rules, and the valid "recommend not building it" outcome are all defined there; use them as written.
How this skill runs
This is a live conversation, not a subagent job — it runs in the main loop. Ask the seven grill questions from the playbook one at a time, in order. Never dump the list at once. Apply the playbook's handling rules on every answer: a vague answer gets narrowed into a forced choice built from the answer's own words before moving on; "everyone" and "it'd be cool" are rejected outright per the playbook.
If the idea fails its own questions — no real user, no real switch reason, no number that would move — say so plainly, name which questions it failed, and recommend against building it. Stop there; do not write IDEA.md for an idea you've just recommended against.
Closing the grill
Once all seven questions produce real answers:
- Write
.planning/IDEA.mdfrom the template atplaybooks/templates/IDEA.md, filling Problem, Exact user, The one action, Why now / why switch, Non-goals, and Success signal from the grill answers. Once written, IDEA.md is locked — do not reinterpret it later. - Update
.planning/STATE.mdfrom the template atplaybooks/templates/STATE.md: set Project to a short working name for the idea (confirm it with the user in one breath before writing it), Phase togrill, Now to "grill complete, IDEA.md locked", Next to "run /aa-new-project", Pointers to.planning/IDEA.md, and Blockers tonone. - Tell the user the grill is done and offer
/aa-new-projectas the next step. State, using the Grill → intake mapping table, exactly which of the 8 intake questions are already pre-filled from this conversation and which three (hard constraints, riskiest unknown, review-batch appetite) will still be asked fresh.
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 · 28 lines · 45 tokens per session scan A 81a37fb4805a
aa-grill is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 626 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.
github-project-management
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning.
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.