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/nguyenvanphituoc/shapeup-sdlc-plugin/shapeupnpx skills add nguyenvanphituoc/shapeup-sdlc-plugin --skill shapeupgit clone --depth 1 https://github.com/nguyenvanphituoc/shapeup-sdlc-pluginWrote 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/nguyenvanphituoc/shapeup-sdlc-plugin/shapeup)<a href="https://agentmods.dev/skills/nguyenvanphituoc/shapeup-sdlc-plugin/shapeup"><img src="https://agentmods.dev/badge/skills/nguyenvanphituoc/shapeup-sdlc-plugin/shapeup.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.00217 | $0.03862 |
| Opus 5 | $0.00109 | $0.01931 |
| Sonnet 5 | $0.00043 | $0.00772 |
| Haiku 4.5 | $0.00022 | $0.00386 |
Grade A, and why
shapeup 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 — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ShapeUp Skill — v2.1
Shape Up workflows for Claude Code — covering every stage from raw problem to wiring diagram to structured handoff documents. Run these before writing code.
Resource Files (Load On Demand)
This skill lazily loads detail from resource files. Read the relevant resource before executing any workflow:
| Sub-command | Resource to Read |
|---|---|
/shapeup shaping |
resources/shaping.md |
/shapeup spike |
resources/spike.md |
/shapeup breadboarding |
resources/breadboarding.md |
/shapeup framing-doc |
resources/framing-doc.md |
/shapeup kickoff-doc |
resources/kickoff-doc.md |
/shapeup breadboard-reflection |
resources/breadboard-reflection.md |
/shapeup full |
Read resources/shaping.md first, then resources/breadboarding.md before B-phases, and resources/context-compaction.md for the run digest |
Resource paths are relative to this skill's directory (
resources/beside this SKILL.md, wherever the plugin is installed). Multi-gate runs maintain a derived decision digest so each gate reads a compact slice instead of full prose — seeresources/context-compaction.mdand the "Run Workspace & Digest" section below.
Canonical Workflow Order
/shaping /breadboarding
───────────────────────── ───────────────────────────────────
1. Problem frame 5. [optional] Fat marker sketch
2. Requirements (R) 6. Affordance tables + wiring
3. Solution shape (A) 7. SLICING → vertical scopes
4. Fit check (R ↔ A)
↓
Spike docs
(for unknowns only)
↓
breadboarding
The single most common mistake: putting slicing inside shaping. Slicing is the final phase of breadboarding — not shaping. Shaping ends at the fit check.
Which Sub-Command to Use
| You have... | Use... |
|---|---|
| A raw idea and want the full shaped pitch | /shapeup full |
| A raw problem or feature idea | /shapeup shaping |
| Shaped solution with unknowns to de-risk first | /shapeup spike |
| Shaped solution ready for concrete wiring | /shapeup breadboarding |
| A transcript of a problem/betting conversation | /shapeup framing-doc |
| A transcript of a shaped project kickoff | /shapeup kickoff-doc |
| An existing breadboard with design smells | /shapeup breadboard-reflection |
What ships with it
7 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.
- 6d ago First seen · 404 lines · 217 tokens per session scan A 419fbdb53ec1
shapeup is a skill published in the GitHub repository nguyenvanphituoc/shapeup-sdlc-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 217 tokens to every session and 3,862 once invoked, about $0.0011 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
agent-swarm-issue
Agent skill for swarm-issue - invoke with $agent-swarm-issue.
agent-swarm
Agent skill for swarm - invoke with $agent-swarm.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
cog-meeting-processing
Process meeting recordings and transcripts into decisions, action items, and team dynamics.
cog-team-intelligence
Cross-reference GitHub, Linear, Slack, and PostHog with bidirectional sync for team briefs.
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.