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 commands/peerjakobsen/smartspender/plan-productgit 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/plan-product)<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/plan-product"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/plan-product.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 | $0.00000 | $0.01102 |
| Opus 5 | $0.00000 | $0.00551 |
| Sonnet 5 | $0.00000 | $0.00220 |
| Haiku 4.5 | $0.00000 | $0.00110 |
Grade A, and why
plan-product 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Product
Establish foundational product documentation through an interactive conversation. Creates mission, roadmap, and tech stack files in agent-os/product/.
Important Guidelines
- Always use AskUserQuestion tool when asking the user anything
- Keep it lightweight — gather enough to create useful docs without over-documenting
- One question at a time — don't overwhelm with multiple questions
Process
Step 1: Check for Existing Product Docs
Check if agent-os/product/ exists and contains any of these files:
mission.mdroadmap.mdtech-stack.md
If any files exist, use AskUserQuestion:
I found existing product documentation:
- mission.md: [exists/missing]
- roadmap.md: [exists/missing]
- tech-stack.md: [exists/missing]
Would you like to:
1. Start fresh (replace all)
2. Update specific files
3. Cancel
(Choose 1, 2, or 3)
If option 2, ask which files to update and only gather info for those. If option 3, stop here.
If no files exist, proceed to Step 2.
Step 2: Gather Product Vision (for mission.md)
Use AskUserQuestion:
Let's define your product's mission.
**What problem does this product solve?**
(Describe the core problem or pain point you're addressing)
After they respond, use AskUserQuestion:
**Who is this product for?**
(Describe your target users or audience)
After they respond, use AskUserQuestion:
**What makes your solution unique?**
(What's the key differentiator or approach?)
Step 3: Gather Roadmap (for roadmap.md)
Use AskUserQuestion:
Now let's outline your development roadmap.
**What are the must-have features for launch (MVP)?**
(List the core features needed for the first usable version)
After they respond, use AskUserQuestion:
**What features are planned for after launch?**
(List features you'd like to add in future phases, or say "none yet")
Step 4: Establish Tech Stack (for tech-stack.md)
First, check if agent-os/standards/global/tech-stack.md exists.
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.
- 4d ago First seen · 205 lines · 0 tokens per session scan A ecd1abef7c3b
plan-product is a command published in the GitHub repository peerjakobsen/smartspender (5 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,102 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
docs
Generate or update OpenAPI spec from existing API routes.
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-r2:presigned-url
Generate presigned URLs for secure client-side uploads or downloads.
bun:migrate
Migrate existing Node.js/npm projects to Bun.
cloudflare-turnstile:setup
Interactive wizard for setting up Cloudflare Turnstile. Generates templates, configuration, and provides step-by-step guidance based on framework and environment.