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 nguyenvanphituoc/shapeup-sdlc-plugin --skill scope-hammergit 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/scope-hammer)<a href="https://agentmods.dev/skills/nguyenvanphituoc/shapeup-sdlc-plugin/scope-hammer"><img src="https://agentmods.dev/badge/skills/nguyenvanphituoc/shapeup-sdlc-plugin/scope-hammer.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.00177 | $0.02532 |
| Opus 5 | $0.00088 | $0.01266 |
| Sonnet 5 | $0.00035 | $0.00506 |
| Haiku 4.5 | $0.00018 | $0.00253 |
Grade A, and why
scope-hammer 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 7d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scope Hammer (GATE H — Decide When to Stop)
The mechanism behind Shape Up step 11: as the appetite/round budget runs out, cut back on perfectionist ambitions by comparing the actual product to the baseline — what customers live with today — not to a hypothetical perfect version. "Better than the baseline" is good enough to ship; "not as good as I imagined" is not a reason to keep building.
Why this is its own skill, not tech-lead prose. GATE H census pulls from several sources
that accumulate over a whole run (QA findings, discovered-task ledger, attempt-budget
overflows, per-scope inner-breaker trips) — a genuinely separate synthesis step from
orchestration. Splitting it out keeps tech-lead thin (it dispatches, this skill decides what
survives the hammer) and gives the census/cut-list/verdict logic one owner instead of being
re-derived inline at every SHIP.
When this fires
1. All scopes reach FINISHED on the hill → normal stop, post-QA-hunt.
2. Outer circuit breaker trips: round_budget reaches 0 with scopes still uphill/downhill.
3. Inner circuit breaker trips: a scope's attempt_budget (default 5) is exhausted without a
T0-green result → queued as a hammer PROPOSAL (`hammer_proposals`),
judged here rather than immediately blocking the round.
Any of the three routes to this skill; the difference is only what's in the census (case 1 has no unresolved scopes; cases 2/3 do, and those become explicit CUT or CARRY candidates below).
Workflow
INPUT: run's finished/unfinished scopes + baseline + census sources
│
⏸ GATE H0 │ Census ──────────────► collect every open item, classify must-have / nice-to-have
│
⏸ GATE H1 │ Baseline Comparison ──► for each unresolved must-have, is the product still
│ better than the baseline without it?
│
⏸ GATE H2 │ Cut List & Verdict ───► propose cuts (PO confirms), ship / carry-to-next-cycle verdict
│
✅ Done └─► cut list + verdict handed to tech-lead SHIP; PO owns the final call
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.
- 7d ago First seen · 187 lines · 177 tokens per session scan A 9be1c29eb013
scope-hammer is a skill published in the GitHub repository nguyenvanphituoc/shapeup-sdlc-plugin (2 stars, last pushed today), licensed MIT. It adds 177 tokens to every session and 2,532 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
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.
convoy-management
Create, track, and land convoys of related beads as primary work orders in the Gas Town multi-agent orchestration framework.