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/command-design)<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/command-design"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/command-design/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/command-design"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/command-design.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.00554 |
| Opus 5.5 | $0.00000 | $0.00222 |
| Sonnet 5.5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
command-design 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command Design Principles
Context
Commands are slash commands that users invoke directly. Each command triggers a specific workflow. This standard defines how to design commands that are intuitive and reliable.
Design Principles
One Command, One Job
Each command should do one clear thing. Don't combine unrelated actions.
Good: /smartspender:sync nykredit -- syncs transactions from one bank
Bad: /smartspender:sync-and-analyze -- combining two distinct workflows
Predictable Arguments
Users should be able to guess valid arguments.
- Bank commands accept bank IDs:
nykredit,danske-bank - Time commands accept months:
january,2026-01 - Service commands accept service names:
netflix,spotify - Use
allas a special argument when applicable:/smartspender:sync all
Clear Feedback
Every command should report what it did when finished.
Good: "Synced 47 new transactions from Nykredit (Jan 15 - Feb 1)" Bad: "Done."
Human-in-the-Loop by Default
Any step that requires authentication or irreversible action should pause for user confirmation.
Required handoff points:
- Bank login (MitID)
- Service login (for cancellation)
- Final cancellation confirmation
- Any action that spends money or changes account settings
Graceful Failure
Commands should handle common failures explicitly:
- No internet / bank site down: "Could not reach Nykredit netbank. Please check your connection."
- Session expired: "Bank session has expired. Please log in again with MitID."
- No new data: "No new transactions found since last sync (Jan 28)."
- MCP not configured: "Google Sheets MCP is not configured. Run /smartspender:add-account first."
Command Naming Rules
- Use verbs for actions:
sync,analyze,cancel - Use nouns for views:
overview,report,subscriptions - Keep names short -- one word when possible
- Use hyphens for multi-word:
add-account - Namespace: all commands use
/smartspender:prefix
Workflow Design Checklist
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 · 62 lines · 0 tokens per session scan A 9cddbaa65632
command-design 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 554 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.