Borrowing it
Nothing to install: this file belongs to mreider/agilemarkdown. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mreider/agilemarkdown/master/.claude/skills/am-plan/SKILL.mdgit clone --depth 1 https://github.com/mreider/agilemarkdownWrote 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/mreider/agilemarkdown/am-plan)<a href="https://agentmods.dev/skills/mreider/agilemarkdown/am-plan"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-plan/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/mreider/agilemarkdown/am-plan"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-plan.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.00071 | $0.00690 |
| Opus 5 | $0.00036 | $0.00345 |
| Sonnet 5 | $0.00014 | $0.00138 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
am-plan 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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
am-plan
The IPM is the short conversation at the start of each iteration where
the team commits to the work. The commit is implicit: it is the rank
order of _priority.md at the moment the iteration starts.
When this fires
- Human says "let's plan", "run IPM", "what's the iteration".
- New iteration is starting.
- User invokes
/am-plan.
What to do
-
Identify the backlog. If multiple, ask which. Most projects have one.
-
Call
sprint_plan(backlog=<name>). The tool returns the rank order, divided into committed (top of priority up to rolling velocity) and below-line (the rest), plus warnings on stories that need attention before the iteration starts. -
Render the result to the human in a clear shape:
Iteration plan: <backlog> velocity <N> / iteration Committed: 1. ★ <title> <type> <pts>p 2. ● <title> <type> <pts>p ... Below the line: <next 3-5 stories> Committed: <total> pts. Velocity: <N>. <Fits | Over by N pts>. -
Surface warnings explicitly. The common ones:
- Oversized feature: a feature has an estimate above 8.
Offer to call the
am-decomposeskill to split it. - Unestimated feature: a feature has no estimate. Ask the human for a Fibonacci value (1, 2, 3, 5, 8). Pivotal pattern: point by uncertainty, not by hours.
- Overcommit: committed points exceed rolling velocity. Offer to trim from the bottom of the committed set.
- Oversized feature: a feature has an estimate above 8.
Offer to call the
-
Wait for the human's response. Loop on edits: the human edits
_priority.md(re-rank) or asks you to fix a story; you re-callsprint_plan; you re-render. The loop ends when the human is satisfied with the plan as rendered. -
The commit moment is implicit. The human says "let's go," or the human starts pulling the first story. Do not write a separate commit artifact.
What NOT to do
- Do not invent estimates. If a story has no estimate, ask the human for one. Do not set one and move on.
- Do not propose splitting a story without offering to call
am-decompose. The decompose skill is the right tool; use it. - Do not pull a story (set_status started) during planning. The planning ceremony is a review; the iteration starts when the human pulls the first story afterwards.
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.
- 9d ago First seen · 76 lines · 71 tokens per session scan A 47579ca8998e
am-plan is a skill published in the GitHub repository mreider/agilemarkdown (7 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 690 once invoked, about $0.0004 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
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…
scrumboy-board-operator
Operate Scrumboy projects and boards through MCP or Agoragentic APIs. Use when an agent needs to inspect board state, plan sprint work, create todos, move cards, manage tags, or summarize project health.
pm-skills
Use when coordinating project-delivery work across the 8 project-management sub-skills — sprint/velocity analytics, portfolio health, Jira/JQL, Confluence, Atlassian admin, templates, meeting analysis, team comms. Triggers on 'our sprints feel off', 'project health report', 'audit our Jira permissions', 'when will it…
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.
sprint-planning
Sprint & Release Planning: Helps with sprint planning, backlog grooming, story estimation, release planning, and roadmap creation. Use this skill whenever the user wants to plan a sprint, groom the backlog, write user stories, estimate tasks, plan a release, create a roadmap, prioritize features, or structure a…
dangerous-animals-of-pm-generator
Generate creature acronyms that name PM dysfunctions, blockers, or winning strategies. Use when you want to give your team shared vocabulary for the animals hiding in your product work.