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/discover-standards)<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/discover-standards"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/discover-standards/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/discover-standards"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/discover-standards.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.01878 |
| Opus 5 | $0.00000 | $0.00939 |
| Sonnet 5 | $0.00000 | $0.00376 |
| Haiku 4.5 | $0.00000 | $0.00188 |
Grade A, and why
discover-standards 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 8d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discover Standards
Extract tribal knowledge from your codebase into concise, documented standards.
Important Guidelines
- Always use AskUserQuestion tool when asking the user anything
- Write concise standards — Use minimal words. Standards must be scannable by AI agents without bloating context windows.
- Offer suggestions — Present options the user can confirm, choose between, or correct. Don't make them think harder than necessary.
Process
Step 1: Determine Focus Area
Check if the user specified an area when running this command. If they did, skip to Step 2.
If no area was specified:
- Analyze the codebase structure (folders, file types, patterns)
- Identify 3-5 major areas. Examples:
- Frontend areas: UI components, styling/CSS, state management, forms, routing
- Backend areas: API routes, database/models, authentication, background jobs
- Cross-cutting: Error handling, validation, testing, naming conventions, file structure
- Use AskUserQuestion to present the areas:
I've identified these areas in your codebase:
1. **API Routes** (src/api/) — Request handling, response formats
2. **Database** (src/models/, src/db/) — Models, queries, migrations
3. **React Components** (src/components/) — UI patterns, props, state
4. **Authentication** (src/auth/) — Login, sessions, permissions
Which area should we focus on for discovering standards? (Pick one, or suggest a different area)
Wait for user response before proceeding.
Step 2: Analyze & Present Findings
Once an area is determined:
-
Read key files in that area (5-10 representative files)
-
Look for patterns that are:
- Unusual or unconventional — Not standard framework/library patterns
- Opinionated — Specific choices that could have gone differently
- Tribal — Things a new developer wouldn't know without being told
- Consistent — Patterns repeated across multiple files
-
Use AskUserQuestion to present findings and let user select:
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.
- 8d ago First seen · 262 lines · 0 tokens per session scan A a3218bba20d1
discover-standards 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,878 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: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.
bun:migrate
Migrate existing Node.js/npm projects to Bun.