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/inject-standardsgit 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/inject-standards)<a href="https://agentmods.dev/commands/peerjakobsen/smartspender/inject-standards"><img src="https://agentmods.dev/badge/commands/peerjakobsen/smartspender/inject-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.01855 |
| Opus 5 | $0.00000 | $0.00928 |
| Sonnet 5 | $0.00000 | $0.00371 |
| Haiku 4.5 | $0.00000 | $0.00186 |
Grade A, and why
inject-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 5d 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inject Standards
Inject relevant standards into the current context, formatted appropriately for the situation.
Usage Modes
This command supports two modes:
Auto-Suggest Mode (no arguments)
/inject-standards
Analyzes context and suggests relevant standards.
Explicit Mode (with arguments)
/inject-standards api # All standards in api/
/inject-standards api/response-format # Single file
/inject-standards api/response-format api/auth # Multiple files
/inject-standards root # All standards in the root folder
/inject-standards root/naming # Single file from root folder
Directly injects specified standards without suggestions.
Note: root is a reserved keyword — it refers to .md files directly in agent-os/standards/ (not in a subfolder).
Process
Step 1: Detect Context Scenario
Before injecting standards, determine which scenario we're in. Read the current conversation and check if we're in plan mode.
Three scenarios:
- Conversation — Regular chat, implementing code, answering questions
- Creating a Skill — Building a
.claude/skills/file - Shaping/Planning — In plan mode, building a spec, running
/shape-spec
Detection logic:
- If currently in plan mode OR conversation clearly mentions "spec", "plan", "shape" → Shaping/Planning
- If conversation clearly mentions creating a skill, editing
.claude/skills/, or building a reusable procedure → Creating a Skill - Otherwise → Ask to confirm (do not assume)
If neither skill nor plan is clearly detected, use AskUserQuestion to confirm:
I'll inject the relevant standards. How should I format them?
1. **Conversation** — Read standards into our chat (for implementation work)
2. **Skill** — Output file references to include in a skill you're building
3. **Plan** — Output file references to include in a plan/spec
Which scenario? (1, 2, or 3)
Always ask when uncertain — don't assume conversation by default.
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.
- 5d ago First seen · 292 lines · 0 tokens per session scan A 334ff2ac64b5
inject-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,855 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:optimize
Interactive Durable Objects performance optimization assistant. Analyzes existing DO code and provides specific optimization recommendations with implementation guidance.
cloudflare-durable-objects:setup
Interactive Durable Objects project initialization. Scaffolds new DO project with proper bindings, migrations, and boilerplate code.
cloudflare-workers:migrate
Platform migration assistant for moving applications from AWS Lambda, Vercel, Netlify, or Cloudflare Pages to Cloudflare Workers.
cloudflare-queues:troubleshoot
Quick troubleshooting for common Cloudflare Queues issues.
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.