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-import)<a href="https://agentmods.dev/skills/peeyushmeher/agent-agile/aa-import"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-import/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-import"><img src="https://agentmods.dev/badge/skills/peeyushmeher/agent-agile/aa-import.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.00047 | $0.00768 |
| Opus 5 | $0.00023 | $0.00384 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
aa-import 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 — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.
aa-import
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 Import path in full, and follow it exactly — do NOT re-derive or improvise the system. That section also depends on The 8 intake questions, Pushback patterns, and Drafting the plan; read those too before starting.
Running the import
The skill's argument is a path to, or description of, the user's existing plan document.
- Read the document in full — no skimming.
- Answer the 8 intake questions from the document alone, without asking the user anything yet. Mark any thinly-answered question as a gap rather than guessing, using the same "thin answer" bar defined in The 8 intake questions.
- Ask the user only the gaps, one question at a time, with the same pushback discipline as a fresh intake.
- Deliver the split statement exactly as defined at the end of planner.md's The 8 intake questions — the "my part / your part" narration plus the process preview — before writing any files. Imported plans get it too: their authors are the users most likely to assume the system does everything.
- Map the result onto the plan format and check the three things Import path names explicitly: whether the Key Results pass the three KR tests, whether every epic has a demo sentence, and whether any existing stories pass the worker-readiness test.
- Write
.planning/PROJECT.md,.planning/ROADMAP.md, and Epic 1's story cards from the templates atplaybooks/templates/PROJECT.md,playbooks/templates/ROADMAP.md, andplaybooks/templates/STORY.md, plus.planning/PREREQS.mdand.planning/CONFIG.mdfrom their templates. Produce a gap list alongside these files — what was missing or broken in the source document — not a silent rewrite. On a multi-epic import, a missing risk register is itself a gap to report: the source plan named no domain edges and no fixtures (seeplaybooks/planner.md"Research fan-out and the risk register"), and the user decides whether to run the fan-out before executing. - Update
.planning/STATE.mdfromplaybooks/templates/STATE.md, Phaseintake.
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 · 34 lines · 47 tokens per session scan A c6a1aa212c8b
aa-import is a skill published in the GitHub repository Peeyushmeher/agent-agile (3 stars, last pushed 1mo ago), licensed MIT. It adds 47 tokens to every session and 768 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.
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…
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.