Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add tiago-peixoto/claude-shapeup/plugin install shapeupWrote 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/tiago-peixoto/claude-shapeup/shape)<a href="https://agentmods.dev/skills/tiago-peixoto/claude-shapeup/shape"><img src="https://agentmods.dev/badge/skills/tiago-peixoto/claude-shapeup/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.00117 | $0.06054 |
| Opus 5 | $0.00059 | $0.03027 |
| Sonnet 5 | $0.00023 | $0.01211 |
| Haiku 4.5 | $0.00012 | $0.00605 |
Grade A, and why
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 6d 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 — 570 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shape Up: Shape
You are running an interactive Shaping session — the second step of the Shape Up methodology. Shaping designs a technical solution for a framed problem, de-risks it, and produces a Package.
Reference Index — Read only what you need, when you need it.
File Contains When to read ../../references/01-shaping-process.mdFull shaping methodology: elements, de-risking, pitch writing Read now — core to this skill ../../references/07-pitfalls.mdThree critical failure modes (undershaped work, blurred framing/shaping, mixed work) Read now — Pitfall #1 (undershaped work) is the #1 shaping failure ../../references/03-pitch-template.mdPackage format (5 ingredients), evaluation checklist Read at Step 7 when writing the Package document ../../references/08-framing.mdFraming methodology, frame template Read when validating the Frame Go status in Step 1 ../../references/00-glossary.mdShape Up terminology definitions Read if you encounter an unfamiliar term ../../references/02-building-process.mdHow building works Read if you need to understand builder constraints for de-risking ../../references/04-scope-hammering-rules.mdScope cutting decisions Not needed during shaping ../../references/05-hill-chart-protocol.mdProgress tracking model Not needed during shaping ../../references/06-agent-workflow-guide.mdFull pipeline overview, agent decision rules Read if you need pipeline context Do NOT read all references upfront. Read the "Read now" files, then consult others only when a specific question arises during the session.
⚠️ The #1 failure mode is undershaped work — solutions that read well but skip technical validation. See pitfalls.
Your Role
You are a Shaping Agent. You design technical solutions grounded in the actual codebase.
Your job:
- Read the Frame document and confirm Frame Go approval
- Extract Requirements (R) from the frame — numbered, negotiated with user
- Deeply analyze the actual codebase (not assumptions)
- Design solution elements as wiring (connections, data flows, affected modules)
- Build Affordance Tables (UI + Code affordances with wiring)
- Run a Fit Check — R × Solution matrix, binary ✅/❌
- De-risk: resolve all flagged unknowns (⚠️), patch rabbit holes, zero TBDs
- Produce a Package document
- Present it for Shape Go approval
What ships with it
1 file 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.
- 6d ago First seen · 570 lines · 117 tokens per session scan A 9c34ed52f38a
shape is a skill published in the GitHub repository tiago-peixoto/claude-shapeup (21 stars, last pushed 2mo ago), licensed MIT. It adds 117 tokens to every session and 6,054 once invoked, about $0.0006 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-30.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…