settings-schema

settings-schema is a command for Claude Code from bengous/claude-code-plugins. It costs 7 tokens per session (717 once invoked), scanned A, original, MIT.

A command for extracting the settings rules used by Claude Code, the command-line coding assistant, from its installed package. It turns those rules into documentation and comparisons.

In plain words
What is it for?
Use it to document a Claude Code version, compare settings across versions, or find settings absent from the official SchemaStore reference.
Why use it?
It helps reveal which settings exist, which are missing from public documentation, and how settings changed between versions.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool; mentions Claude Code.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the claude-settings-manager plugin — 2 commands shipped together

Good fit Use it to document a Claude Code version, compare settings across versions, or find settings absent from the official SchemaStore reference.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add bengous/claude-code-plugins
Claude Code
/plugin install claude-settings-manager

Made for: Claude Code.

Or install claude-settings-manager, the plugin that ships this one along with the rest of its 2 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 settings-schema

README.md
[![agentmods](https://agentmods.dev/badge/commands/bengous/claude-code-plugins/settings-schema/github.svg)](https://agentmods.dev/commands/bengous/claude-code-plugins/settings-schema)
Your own site
<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/settings-schema"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/settings-schema/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.

agentmods 80×15 button for settings-schema

Your own site · 80×15
<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/settings-schema"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/settings-schema.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 717 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.00007 $0.00717
Opus 5.5 $0.00003 $0.00287
Sonnet 5.5 $0.00001 $0.00143
Haiku 4.5 $0.00001 $0.00072

Measured 1mo ago against content hash 94c1bcbc7e78, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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-settings-manager/commands/settings-schema.md · 116 lines

How it starts

The opening of the file, as written. The whole thing — 116 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:

  1. Generate documentation for all available settings
  2. Find undocumented settings not in the official schemastore.org schema
  3. 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:

  1. For extraction: Show a summary of what was extracted:

    • Total describe strings found
    • Property mappings discovered
    • File locations
  2. For comparison: Highlight:

    • New settings in the compared version
    • Removed settings
    • New describe strings

Read the full file on GitHub · 116 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. 1mo ago Changed · -3 lines 94c1bcbc7e78
  2. 1mo ago First seen · 119 lines · 7 tokens per session scan A efedbed37bc6

Subscribe to this mod's changes

settings-schema is a command published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 7 tokens to every session and 717 once invoked, about $0.0000 per session on Opus 5.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.