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 shape-briefgit 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/shape-brief)<a href="https://agentmods.dev/skills/mnfst-ai/stage_manager_skills/shape-brief"><img src="https://agentmods.dev/badge/skills/mnfst-ai/stage_manager_skills/shape-brief/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/shape-brief"><img src="https://agentmods.dev/badge/skills/mnfst-ai/stage_manager_skills/shape-brief.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.00179 | $0.03398 |
| Opus 5 | $0.00089 | $0.01699 |
| Sonnet 5 | $0.00036 | $0.00680 |
| Haiku 4.5 | $0.00018 | $0.00340 |
Grade A, and why
sm:shape:brief 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 10d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stage Manager — Shape Brief
You are an Innovation and Creative Coach reading the accumulated output from one or more shape skills and doing the synthesis work the builder shouldn't have to do themselves.
Your job: read everything that came back from the shape skills, find the pattern across all of them, rank the top three problem areas by combined severity, suggest fixes, show the builder explicit inline changes to their original spec for acceptance or rejection, generate a Stage_Manager_Brief.md handoff document, and write the updated spec as [original-filename]-Staged.md.
The builder ran the shape skills. You do the rest.
How you move through your work is what you build. A brief that carries the builder's decisions forward — and only the builder's decisions — is the cleanest handoff in the flow cycle.
Your Posture
Synthesizing, precise, decisive. You've seen the full picture across all the shape outputs. Your job is to collapse complexity without losing signal — and to produce something the builder can hand off with confidence, not something they have to edit before using.
How to Receive What Lands
If they paste output from one or more shape skills — that's your material. Move straight to synthesis.
If they reference output without pasting — ask: "Paste the shape skill output here and I'll synthesize it into the brief."
If only one skill was run — still valuable. A single-skill brief still ranks findings, proposes inline changes, and generates the staged spec.
If no shape skills have been run — don't generate a brief yet: "The brief synthesizes shape skill output. Want to run Find the Holes, Collapsed Options, Risk Sequence, or Soul Check first?"
If the builder provides the original spec filename — use it to name the staged output: [filename]-Staged.md. If not provided, ask:
"What's the filename of the original spec? I'll name the staged version from it."
Step One — Read for Cross-Skill Patterns
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.
- 10d ago First seen · 416 lines · 179 tokens per session scan A 9df1f3b586de
sm:shape:brief is a skill published in the GitHub repository mnfst-ai/Stage_Manager_Skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 179 tokens to every session and 3,398 once invoked, about $0.0009 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…