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 agentmods add skills/marchatton/agent-skills/wf-shapenpx skills add marchatton/agent-skills --skill wf-shapegit clone --depth 1 https://github.com/marchatton/agent-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/marchatton/agent-skills/wf-shape)<a href="https://agentmods.dev/skills/marchatton/agent-skills/wf-shape"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/wf-shape.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.00064 | $0.01269 |
| Opus 5 | $0.00032 | $0.00634 |
| Sonnet 5 | $0.00013 | $0.00254 |
| Haiku 4.5 | $0.00006 | $0.00127 |
Grade A, and why
wf-shape 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 5d 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wf-shape
Purpose
Turn messy inputs into a shaped packet that is ready for commit-ready planning (wf-plan) or, for small/low-risk work, ready to go straight into wf-develop driven by prd.json.
Optimise for:
- picking the problems/opportunities that create high user and/or business value
- de-scope (draw the perimeter)
- risks understood (rabbit holes surfaced + treated)
- concrete artefacts (brief + breadboard + spikes)
- PRD spine that agents can actually execute against
Inputs
- Raw notes, feature idea, bug report, links
- Constraints + appetite/timebox
- Any existing artefacts (designs, metrics, incidents)
Outputs (dossier)
Create/update a dossier folder:
docs/04-projects/<lane>/<id>_<slug>/
Files:
brief.md(1–2 pager)breadboard-pack.mdrisk-register.mdspike-investigation.md(optional; single file)prd.md(can be one or many)prd.json(recommended; created viacreate-json-prd) (can be one or many)
Steps
- Pickup (recommended if resuming / new thread)
- Understand where we are in the process.
- If new, start at step 1.
- Otherwise start at the relevant step (usually step 8), but first ensure previous steps have been completed.
- Start a dossier (if not created already)
- Choose
id_<slug>(prefer0001_<short>). - Choose a lane under
docs/04-projects/. - Create dossier + stub files.
- Write the 1–2 pager brief
- Inputs should come from the user by invoking
ask-questions-if-underspecifiedand/or using relevant context. - Write
brief.md. - Hard requirements:
- goals + non-goals
- in-scope/out-of-scope perimeter
- top risks + unknowns
- open questions
- GO/NO-GO placeholder
- Breadboard
- Invoke breadboarding skill.
- Save as
breadboard-pack.md(places/affordances/connections + parts list + rabbit holes + fit check).
- Risk register
- Write
risk-register.md. - For every top risk choose: Cut / Patch / Spike / Out-of-bounds.
- Spike investigation (only for Spike items)
- Invoke spike-investigation skill for each Spike.
- Record results in
spike-investigation.md.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 142 lines · 64 tokens per session scan A b28f742cf537
wf-shape is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 5mo ago), licensed MIT. It adds 64 tokens to every session and 1,269 once invoked, about $0.0003 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…
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…