workflow-claude-settings

A command for checking whether a local Claude Code settings report has drifted from selected documentation, CLI references, and changelog versions. It reads the sources and reports differences before making changes.

In plain words
What is it for?
Reviewing recent Claude Code settings changes, comparing the local reference with external documentation and the changelog, and producing a unified drift report.
Why use it?
It identifies outdated or missing settings information without changing the report automatically.

Command for Claude Code

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.

agentmods
npx agentmods add commands/shanraisshan/claude-code-best-practice/workflow-claude-settings
Clone the repo
git clone --depth 1 https://github.com/shanraisshan/claude-code-best-practice

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,490 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00011 $0.03490
Opus 5 $0.00005 $0.01745
Sonnet 5 $0.00002 $0.00698
Haiku 4.5 $0.00001 $0.00349

Measured 2d ago against content hash 818e5e1661cf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

workflow-claude-settings 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 2d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/workflows/best-practice/workflow-claude-settings.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Changelog — Settings Report

You are a coordinator for the claude-code-best-practice project. Your job is to launch two research agents in parallel, wait for their results, merge findings, and present a unified report about drift in the Settings Reference report (best-practice/claude-settings.md).

Versions to check: $ARGUMENTS (default: 10 if empty or not a number)

This is a read-then-report workflow. Launch agents, merge results, and produce a report. Only take action if the user approves.


Phase 0: Launch Both Agents in Parallel

Immediately spawn both agents using the Task tool in the same message (parallel launch):

Agent 1: workflow-claude-settings-agent

Spawn using subagent_type: "workflow-claude-settings-agent". Give it this prompt:

Research the claude-code-best-practice project for settings report drift. Check the last $ARGUMENTS versions (default: 10).

Fetch these 3 external sources:

  1. Settings Documentation: https://code.claude.com/docs/en/settings
  2. CLI Reference: https://code.claude.com/docs/en/cli-reference
  3. Changelog: https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md

Then read the local report file (best-practice/claude-settings.md) and the CLAUDE.md file. Analyze differences between what the official docs say about settings keys, permission syntax, hook events, MCP configuration, sandbox options, plugin settings, model aliases, display settings, and environment variables versus what our report documents. Return a structured findings report covering missing settings, changed types/defaults, new settings additions, deprecated settings, permission syntax changes, hook event changes, MCP setting changes, sandbox setting changes, environment variable completeness, example accuracy, settings hierarchy accuracy, and sources validity.

Agent 2: claude-code-guide

Spawn using subagent_type: "claude-code-guide". Give it this prompt:

Research the latest Claude Code settings system. I need you to find:

  1. The complete list of all currently supported settings.json keys with their types, defaults, and descriptions
  2. Any new settings keys introduced in recent Claude Code versions
  3. Changes to existing settings behavior (e.g. new permission modes, new hook events, new sandbox options)
  4. Changes to the settings hierarchy (new priority levels, new file locations)
  5. Changes to permission syntax (new tool patterns, new wildcard behavior)
  6. New hook events or changes to hook configuration structure
  7. Changes to MCP server configuration (new matching fields, new settings)
  8. Changes to sandbox settings (new network options, new commands)
  9. Changes to plugin configuration (new fields, new marketplace options)
  10. Changes to environment variables (new vars, deprecated vars, changed behavior)
  11. Changes to model aliases or model configuration
  12. Changes to display/UX settings (status line, spinners, progress bars)
  13. Any deprecations or removals of settings keys

Be thorough — search the web, fetch docs, and provide concrete version numbers and details for everything you find.

Read the full file on GitHub · 244 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. 2d ago First seen · 244 lines · 11 tokens per session scan A 818e5e1661cf

Subscribe to this mod's changes

workflow-claude-settings is a command published in the GitHub repository shanraisshan/claude-code-best-practice (65,460 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 3,490 once invoked, about $0.0001 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-30.