index-standards

index-standards is a command for Claude Code from peerjakobsen/smartspender. It costs 0 tokens per session (778 once invoked), scanned A, original, MIT.

A command for rebuilding an index of standards files, where standards are written project rules or guidelines.

In plain words
What is it for?
It helps scan agent-os/standards/, add new standards, retain existing descriptions, and remove entries for deleted files.
Why use it?
It keeps the index aligned with the standards that exist, so other commands can find relevant guidance without reading every file.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: names the AskUserQuestion tool.

Part of the smartspender plugin — 13 skills, 19 commands shipped together

Good fit It helps scan agent-os/standards/, add new standards, retain existing descriptions, and remove entries for deleted files.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/peerjakobsen/smartspender/index-standards
Install

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.

Clone the repo
git clone --depth 1 https://github.com/peerjakobsen/smartspender

Made for: Claude Code.

Or install smartspender, the plugin that ships this one along with the rest of its 13 skills, 19 commands.

Wrote 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.

agentmods badge for index-standards

README.md
[![agentmods](https://agentmods.dev/badge/commands/peerjakobsen/smartspender/index-standards.svg)](https://agentmods.dev/commands/peerjakobsen/smartspender/index-standards)
Your own site
<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>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 778 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 7d ago against content hash adf483013262, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

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.

.claude/commands/agent-os/index-standards.md · 125 lines

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

  1. List all .md files in agent-os/standards/ and its subfolders
  2. 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:

  1. Read the file to understand its content
  2. 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:

  1. List them for the user
  2. 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

Read the full file on GitHub · 125 lines

Changes

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.

  1. 7d ago First seen · 125 lines · 0 tokens per session scan A adf483013262

Subscribe to this mod's changes

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.