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/bengous/claude-code-plugins/settings-schemagit clone --depth 1 https://github.com/bengous/claude-code-pluginsWhat 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.00007 | $0.00738 |
| Opus 5 | $0.00003 | $0.00369 |
| Sonnet 5 | $0.00001 | $0.00148 |
| Haiku 4.5 | $0.00001 | $0.00074 |
Grade A, and why
settings-schema 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 yesterday.
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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Settings Schema Extraction
You are extracting and analyzing Claude Code's settings schema from the npm package bundle.
Background
Claude Code's settings are validated using Zod schemas. These schemas contain .describe() strings that document each setting. This command extracts those descriptions from the minified cli.js bundle to:
- Generate documentation for all available settings
- Find undocumented settings not in the official schemastore.org schema
- Compare schemas between versions
Your Task
Step 1: Determine What the User Wants
If the user hasn't specified, ask what they want to do:
Use AskUserQuestion:
Question: "What would you like to do with the Claude Code schema?"
Options:
- "Extract schema from current/specific version (generate docs)"
- "Compare versions (find new/removed settings)"
- "Find undocumented settings (diff against schemastore.org)"
Step 2: Get Version Information
Check the current Claude Code version:
claude --version
If user wants a specific version, they can provide it. Otherwise use "latest".
Step 3: Execute the Appropriate Command
For schema extraction:
"${CLAUDE_PLUGIN_ROOT}/scripts/settings-manager" schema-extract \
--version <VERSION> \
--output-dir <OUTPUT_DIR> \
--format both
Default output directory: current directory or user-specified.
For version comparison:
"${CLAUDE_PLUGIN_ROOT}/scripts/settings-manager" schema-diff \
--base <VERSION1> \
--compare <VERSION2>
For finding undocumented settings:
"${CLAUDE_PLUGIN_ROOT}/scripts/settings-manager" schema-diff \
--base schemastore \
--compare latest
Step 4: Present Results
After extraction, read and summarize the generated files:
-
For extraction: Show a summary of what was extracted:
- Total describe strings found
- Property mappings discovered
- File locations
-
For comparison: Highlight:
- New settings in the compared version
- Removed settings
- New describe strings
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.
- yesterday First seen · 119 lines · 7 tokens per session scan A efedbed37bc6
settings-schema is a command published in the GitHub repository bengous/claude-code-plugins (4 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 738 once invoked, about $0.0000 per session on Opus 5. 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
pr-address
Address PR review comments on current branch.
plan-save
Save the current session's plan to GitHub as an issue.
enforce_standards
CRITICAL: Before running the code standards enforcer, we must prepare the stack properly and abort if there are merge conflicts.
OPSX: Sync
Sync delta specs from a change to main specs.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
OPSX: Verify
Verify implementation matches change artifacts before archiving.