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-accept/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-accept)<a href="https://agentmods.dev/skills/mreider/agilemarkdown/am-accept"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-accept.svg" alt="Measured on agentmods" 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.00072 | $0.00469 |
| Opus 5 | $0.00036 | $0.00234 |
| Sonnet 5 | $0.00014 | $0.00094 |
| Haiku 4.5 | $0.00007 | $0.00047 |
Grade A, and why
am-accept 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 7d 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
am-accept
The agent is the dev pair. The human is the PM. The agent does NOT flip
a story to accepted directly. Acceptance is a moment that belongs to
the human. This skill stages the moment.
When this fires
- Human asks to accept a story.
- Human asks "is X done?" about a delivered story.
- Agent just transitioned a story to
deliveredand the user is still in the loop. - User invokes
/am-accept.
What to do
-
Identify the story path. Use
list_itemsorpriority_listif needed to disambiguate. Insist on exactly one path. -
Read the story with
get_item(path). Surface to the human:- title, type, current status, estimate
- the first line or two of the body so they remember the intent
-
Ask the human one question: "As PM, do you accept this story?"
-
On yes: call
set_status(path, "accepted"). -
On no: call
reject_item(path, reason="..."). The reason lands in the body's## Rejection notessection so the team can see why.
What NOT to do
- Do not call
set_statustoacceptedbefore getting the human's yes. - Do not summarize the diff for the human in your own words; let them look at the diff themselves.
- Do not propose a new estimate as part of acceptance. Acceptance is yes-or-no on the work as delivered.
In solo mode
The same human is both the dev's pair and the PM. Render the question anyway. The pause is the point. The agent does not enforce a mode toggle; it trusts the human to answer with care.
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.
- 7d ago First seen · 54 lines · 72 tokens per session scan A c1c87ddb428d
am-accept is a skill published in the GitHub repository mreider/agilemarkdown (7 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 469 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.