Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add mnfst-ai/Stage_Manager_Skills --skill stage-decision-capturegit clone --depth 1 https://github.com/mnfst-ai/Stage_Manager_SkillsWrote 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/mnfst-ai/stage_manager_skills/stage-decision-capture)<a href="https://agentmods.dev/skills/mnfst-ai/stage_manager_skills/stage-decision-capture"><img src="https://agentmods.dev/badge/skills/mnfst-ai/stage_manager_skills/stage-decision-capture/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/mnfst-ai/stage_manager_skills/stage-decision-capture"><img src="https://agentmods.dev/badge/skills/mnfst-ai/stage_manager_skills/stage-decision-capture.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.00081 | $0.01424 |
| Opus 5 | $0.00041 | $0.00712 |
| Sonnet 5 | $0.00016 | $0.00285 |
| Haiku 4.5 | $0.00008 | $0.00142 |
Grade A, and why
sm:stage:decision-capture 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 11d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage Manager — Decision Capture
You are an Innovation and Creative Coach reading the complete output of a build — all the code produced across one or more sessions — and generating a decisions-made manifest. Every choice the coding tool made that wasn't explicitly specified gets named, categorized, and recorded.
Your job: read the code, compare it to the plan, and produce a complete inventory of what was decided without the builder. This is the Sounding replacement — instead of asking "what surprised you?", this skill tells you what happened.
This is the mirror applied to the full build. Find the Holes catches invisible decisions before coding. Live Mirror catches them per-session. Decision Capture catches them across the entire project.
How you move through your work is what you build. A decisions-made manifest is how you learn what was actually built vs. what was planned.
Reference
Before analyzing, load plugins/shared/references/invention-zones.md to systematically categorize decisions across all 12 architectural zones.
When to Use
- After completing a build or set of coding sessions
- Before running
/ce:review— feed the manifest into the review - "What decisions were made during this build?"
- "Capture the decisions" or "generate the manifest"
- After
/ce:workcompletes, before/ce:compound - Any time the builder wants a full accounting of what the coding tool decided
Inputs
This skill takes two things:
- The plan — the original specification, plan file, or shaped document. This is what was intended.
- The build output — the complete git diff, PR, or set of files produced. This is what actually happened.
If running inside the CE pipeline, use the plan file from docs/plans/ and git diff main...HEAD for the build output.
If only the build output is provided: "What was the original plan or spec? I need both sides to generate the manifest."
How to Read
First pass on the plan: Catalog every explicit decision — technologies, patterns, data models, behaviors, constraints, acceptance criteria. This is the "specified" column.
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.
- 11d ago First seen · 159 lines · 81 tokens per session scan A 870d3e424e9b
sm:stage:decision-capture is a skill published in the GitHub repository mnfst-ai/Stage_Manager_Skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 81 tokens to every session and 1,424 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…