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-inception/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-inception)<a href="https://agentmods.dev/skills/mreider/agilemarkdown/am-inception"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-inception/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-inception"><img src="https://agentmods.dev/badge/skills/mreider/agilemarkdown/am-inception.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.00076 | $0.00641 |
| Opus 5 | $0.00038 | $0.00320 |
| Sonnet 5 | $0.00015 | $0.00128 |
| Haiku 4.5 | $0.00008 | $0.00064 |
Grade A, and why
am-inception 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
am-inception
An inception is the conversation that frames a project. The output is
a one-page document at inception.md covering six sections. This skill
runs the conversation; the human answers; the doc lands on disk.
When this fires
- Human says "let's run an inception" or starts a new project.
- Repo has no
inception.mdand the human is about to plan stories. - User invokes
/am-inception.
What to do
-
Check whether
inception.mdalready exists. Callinception_doc()(no body argument). If existed=true, ask the human whether to read the current doc or rewrite it. Default: read. -
If the doc does not exist or the human wants to rewrite, walk the six questions one at a time. Ask each, wait, write the answer down. Do not move on until the human answers.
-
The user. "Who, specifically, are we building this for? Not a demographic. A real person with real circumstances."
-
The goal. "What changes for that user when we ship? Make it observable."
-
The reason. "Why this, why now? What changes if we do not ship this?"
-
Success. "How will we know it worked? The smallest signal you would believe."
-
Constraints. "What can't move? Budget, deadline, regulator, dependency."
-
Out of scope. "What are we explicitly not doing? Naming this saves arguments later."
-
-
Assemble the answers into the inception template shape (six
##headings with the human's text under each) and write the doc withinception_doc(body=<assembled body>). -
Confirm: print the doc back to the human and ask whether to commit it (the human commits via git; you do not run git from the agent).
What NOT to do
- Do not invent answers. If the human says "I don't know," that is the answer; record it and move on. The inception is more useful with honest gaps than with confident fabrications.
- Do not write stories yet. The inception produces a one-pager. Stories come later, once the team is ready to plan the first iteration.
- Do not skip the "Out of scope" section. It is the most useful one in retrospect. If the human says "nothing", push: "really, nothing? what are we deliberately not doing?"
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 · 71 lines · 76 tokens per session scan A 6bf8dd7eb460
am-inception is a skill published in the GitHub repository mreider/agilemarkdown (7 stars, last pushed 3mo ago), licensed MIT. It adds 76 tokens to every session and 641 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…
productspec
Use when implementing, reviewing, planning, or changing work governed by a Product Spec. Treat .product-spec.md files as the product contract for the work.
productspec-authoring
Writes, validates, and converts ProductSpec files (.product-spec.md), the Markdown format for recording product intent before implementation. Use when authoring a new Product Spec, converting an existing PRD or feature doc into one, validating spec files locally or in CI, or recording how a spec's intent changed over…
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.