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/index-standards)<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/index-standards"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/index-standards.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.1 | $0.00000 | $0.00778 |
| Opus 5 | $0.00000 | $0.00389 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
index-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 7d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Index Standards
Rebuild and maintain the standards index file (index.yml).
Purpose
The index enables /inject-standards to suggest relevant standards without reading all files. It maps each standard to a brief description for quick matching.
Process
Step 1: Scan for Standards Files
- List all
.mdfiles inagent-os/standards/and its subfolders - Build a list of all standards organized by folder:
root/coding-style.md # Files in standards/ root use "root" as the folder name root/naming.md api/response-format.md api/error-handling.md database/migrations.md
Note: root is a reserved keyword — it refers to .md files directly in agent-os/standards/ (not in a subfolder). Do not create an actual folder named "root".
Step 2: Load Existing Index
Read agent-os/standards/index.yml if it exists. Note which entries already have descriptions.
Step 3: Identify Changes
Compare the file scan with the existing index:
- New files — Standards files without index entries
- Deleted files — Index entries for files that no longer exist
- Existing files — Already indexed, keep as-is
Step 4: Handle New Files
For each new standard file that needs an index entry:
- Read the file to understand its content
- Use AskUserQuestion to propose a description:
New standard needs indexing:
File: api/response-format.md
Suggested description: "API response envelope structure and error format"
Accept? (yes / or type a better description)
Keep descriptions to one short sentence — they're for matching, not documentation.
Step 5: Handle Deleted Files
If there are index entries for files that no longer exist:
- List them for the user
- Remove them from the index automatically (no confirmation needed)
Report: "Removed 2 stale index entries: api/old-pattern.md, testing/deprecated.md"
Step 6: Write Updated Index
Generate agent-os/standards/index.yml with this structure:
folder-name:
file-name:
description: Brief description here
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.
- 7d ago First seen · 125 lines · 0 tokens per session scan A adf483013262
index-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 778 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.