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.
git clone --depth 1 https://github.com/peerjakobsen/smartspenderWrote 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/commands/peerjakobsen/smartspender/shape-spec)<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/shape-spec"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/shape-spec/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/commands/peerjakobsen/smartspender/shape-spec"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/shape-spec.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.00000 | $0.01525 |
| Opus 5.5 | $0.00000 | $0.00610 |
| Sonnet 5.5 | $0.00000 | $0.00305 |
| Haiku 4.5 | $0.00000 | $0.00153 |
Grade A, and why
shape-spec 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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shape Spec
Gather context and structure planning for significant work. Run this command while in plan mode.
Important Guidelines
- Always use AskUserQuestion tool when asking the user anything
- Offer suggestions — Present options the user can confirm, adjust, or correct
- Keep it lightweight — This is shaping, not exhaustive documentation
Prerequisites
This command must be run in plan mode.
Before proceeding, check if you are currently in plan mode.
If NOT in plan mode, stop immediately and tell the user:
Shape-spec must be run in plan mode. Please enter plan mode first, then run /shape-spec again.
Do not proceed with any steps below until confirmed to be in plan mode.
Process
Step 1: Clarify What We're Building
Use AskUserQuestion to understand the scope:
What are we building? Please describe the feature or change.
(Be as specific as you like — I'll ask follow-up questions if needed)
Based on their response, ask 1-2 clarifying questions if the scope is unclear. Examples:
- "Is this a new feature or a change to existing functionality?"
- "What's the expected outcome when this is done?"
- "Are there any constraints or requirements I should know about?"
Step 2: Gather Visuals
Use AskUserQuestion:
Do you have any visuals to reference?
- Mockups or wireframes
- Screenshots of similar features
- Examples from other apps
(Paste images, share file paths, or say "none")
If visuals are provided, note them for inclusion in the spec folder.
Step 3: Identify Reference Implementations
Use AskUserQuestion:
Is there similar code in this codebase I should reference?
Examples:
- "The comments feature is similar to what we're building"
- "Look at how src/features/notifications/ handles real-time updates"
- "No existing references"
(Point me to files, folders, or features to study)
If references are provided, read and analyze them to inform the plan.
Step 4: Check Product Context
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 · 268 lines · 0 tokens per session scan A fbe80764a0b3
shape-spec is a command published in the GitHub repository peerjakobsen/smartspender (5 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,525 tokens. 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 commands, from other repositories
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:optimize
Analyze and optimize Cloudflare Workers performance. Checks bundle size, caching, memory usage, and provides actionable recommendations.
better-auth:add-plugin
Add a better-auth plugin to an existing project. Configures server and client plugins with proper imports.
better-auth:setup
Interactive setup wizard for better-auth authentication. Guides through database, framework, OAuth providers, and plugin configuration.
cloudflare-workflows:create
Quick scaffold for new workflow class in existing project. Use when user wants to add another workflow to existing project without full setup wizard.
cloudflare-r2:presigned-url
Generate presigned URLs for secure client-side uploads or downloads.