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 saski/arnesto --skill shape-upgit clone --depth 1 https://github.com/saski/arnestoWrote 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/saski/arnesto/shape-up)<a href="https://agentmods.dev/skills/saski/arnesto/shape-up"><img src="https://agentmods.dev/badge/skills/saski/arnesto/shape-up/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/saski/arnesto/shape-up"><img src="https://agentmods.dev/badge/skills/saski/arnesto/shape-up.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.00085 | $0.00565 |
| Opus 5.5 | $0.00034 | $0.00226 |
| Sonnet 5.5 | $0.00017 | $0.00113 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
shape-up 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 1mo 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.
This is a copy
100% identical to shape-up — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domain Context
This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.
Input Requirements
- Context about your product, feature, or problem
- Relevant data, research, or constraints (recommended but optional)
- Clear articulation of what you're trying to achieve
Shape Up
What It Is
Shape Up is a product development methodology built on one core insight: you cannot estimate your way to shipping—you must shape your way there.
Traditional approaches ask "How long will this take?" and then try to hit that estimate. Shape Up flips this: decide upfront how much time you're willing to spend (the appetite), then shape a version of the solution that fits within that constraint.
The methodology emerged from 17 years of building Basecamp, where the founding team faced an unusual constraint: their only engineer (DHH) worked just 10 hours per week. This forced extreme clarity about what to build and ruthless scoping to ensure every hour counted.
The key shift: Move from "What's the estimate for this?" to "What version of this can we confidently ship in the time we're willing to spend?"
When to Use It
Use Shape Up when you need to:
- Stop projects from dragging — work that should take weeks is taking months
- Escape the estimate trap — you're tired of estimates that are always wrong
- Give teams real autonomy — not just ticket execution
- Reduce meeting overhead — Scrum rituals are consuming your time
- Ship meaningful chunks — not just incremental tickets
- Align product and engineering — there's a wall between them today
- Maintain startup speed — as you scale past 30-50 people
When Not to Use It
- You're 3 people or fewer — just talk to each other
- There's no real complexity
- You can't get engineering into shaping
- Leadership isn't bought in
- You're doing pure maintenance
Resources
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.
- 1mo ago First seen · 59 lines · 85 tokens per session scan A 75aee8332714
shape-up is a skill published in the GitHub repository saski/arnesto (6 stars, last pushed 4d ago), licensed Unlicense. It adds 85 tokens to every session and 565 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to shape-up, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
work-state-and-delivery
Use when designing or reconciling design docs, task boards, external trackers, execution plans, delivery records, handoffs, review evidence, task-to-change traceability, or repository commit-coupling policy.
requirements-writer
Use when converting PM intake into a slice SPEC.md with observable acceptance outcomes, explicit scope, and advisory sibling build dependencies.
queue-handoff
Use when ending a turn, finishing a slice, blocked on another agent's work, or escalating to a human — durable work handoff via queue items so the system keeps moving across compactions, missed messages, and interruptions. Covers the hot-potato terminal-turn-rule (active work ends by passing the ball, not by going…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
machinist
Use Machinist to create, assign, and monitor software tasks. Use when a coding agent needs to work with Machinist, its GitHub issue workflow, intake labels, direct runs, or managed queue.
document-to-action-items
Extract cited facts, obligations, deadlines and proposed tasks from contracts, reports, forms and scans, keeping page citations, how binding each item is (may/should/must) and unclear scan text visible.