agentmods.dev

agilemarkdown: Skill for Claude Code

.claude/skills/am-accept/SKILL.md

am-accept is a skill for Claude Code from mreider/agilemarkdown. It costs 72 tokens per session (469 once invoked), scanned A, original, MIT.

A review step for a completed Agile Markdown story, where the human product manager decides whether to accept or reject it.

In plain words
What is it for?
It helps inspect a delivered story, ask for the product manager's decision, mark it accepted after a yes, or record rejection notes after a no.
Why use it?
It keeps approval separate from coding so the agent cannot declare its own work accepted.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is mreider/agilemarkdown's own configuration. It tells Claude Code how to work on agilemarkdown itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything agilemarkdown configures →

not rated 8repo 4mo ago A scan 72 tokens original MIT
View source ↗ mreider/agilemarkdown agilemarkdown.com
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/mreider/agilemarkdown/master/.claude/skills/am-accept/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/mreider/agilemarkdown

Made for: Claude Code.

Wrote 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.

agentmods badge for am-accept

README.md
[![agentmods](https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-accept/github.svg)](https://agentmods.dev/skills/mreider/agilemarkdown/am-accept)
Your own site
<a href="https://agentmods.dev/skills/mreider/agilemarkdown/am-accept"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-accept/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.

agentmods 80×15 button for am-accept

Your own site · 80×15
<a href="https://agentmods.dev/skills/mreider/agilemarkdown/am-accept"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-accept.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.00469
Opus 5.5 $0.00029 $0.00188
Sonnet 5.5 $0.00014 $0.00094
Haiku 4.5 $0.00007 $0.00047

Measured 2mo ago against content hash c1c87ddb428d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

.claude/skills/am-accept/SKILL.md · 54 lines

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 delivered and the user is still in the loop.
  • User invokes /am-accept.

What to do

  1. Identify the story path. Use list_items or priority_list if needed to disambiguate. Insist on exactly one path.

  2. 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

  3. Ask the human one question: "As PM, do you accept this story?"

  4. On yes: call set_status(path, "accepted").

  5. On no: call reject_item(path, reason="..."). The reason lands in the body's ## Rejection notes section so the team can see why.

What NOT to do

  • Do not call set_status to accepted before 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.

Changes

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.

  1. 2mo ago First seen · 54 lines · 72 tokens per session scan A c1c87ddb428d

Subscribe to this mod's changes

am-accept is a skill published in the GitHub repository mreider/agilemarkdown (8 stars, last pushed 4mo ago), licensed MIT. It adds 72 tokens to every session and 469 once invoked, about $0.0003 per session on Opus 5.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.

Project managementagilemarkdownproduct-managementscrum
Related

am-accept compared with skills from other repositories

am-accept next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
am-acceptmreider/agilemarkdownSkill84mo agoMITA72Claude Code
gr-product-dev-opsGingiris-1031/gingiris-skillsSkill892d agoMITA576Claude Code, Codex
scrumboy-board-operatormarkrai/scrumboySkill448yesterdayAGPL-3.0A51Claude Code
pm-skillsmrDesign-ww/vault-osSkill39d agoMITA179Claude Code
productspecgokulrajaram/ProductSpecSkill3173mo agoMITA35Claude Code, Codex
productspec-authoringgokulrajaram/ProductSpecSkill3173mo agoMITA90Claude Code, Codex
project-managerbuiphucminhtam/forgewrightSkill496d agononeA68Claude Code