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.
/plugin marketplace add bengous/claude-code-plugins/plugin install claude-settings-managerWrote 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/bengous/claude-code-plugins/settings-setup)<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/settings-setup"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/settings-setup/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.
<a href="https://agentmods.dev/commands/bengous/claude-code-plugins/settings-setup"><img src="https://agentmods.dev/badge/commands/bengous/claude-code-plugins/settings-setup.svg" alt="Reviewed on agentmods" width="80" 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.00009 | $0.01365 |
| Opus 5.5 | $0.00004 | $0.00546 |
| Sonnet 5.5 | $0.00002 | $0.00273 |
| Haiku 4.5 | $0.00001 | $0.00136 |
Grade B, and why
settings-setup scanned grade B with 1 finding 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 24d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Read(~/.claude/settings.json) How it starts
The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Settings Setup Wizard
You are setting up a JSONC workflow for Claude Code settings in this repository.
The JSONC Workflow
Claude Code's settings.json doesn't support comments. This workflow:
- Maintains
__settings.jsoncas the editable source (supports//and/* */comments) - Auto-generates
settings.jsonvia hooks - Blocks direct edits to prevent drift
Your Task
Step 1: Analyze the Repository
Explore the repo to understand its structure. Check:
-
Repo type detection:
- Is there a
.chezmoi.yaml.tmpl,.chezmoi.toml.tmpl, or.chezmoiroot? (chezmoi dotfiles) - Are there
dot_*prefixed directories? (chezmoi dotfiles) - Is there a
stowor package-based structure? (stow dotfiles) - Otherwise: regular project repo
- Is there a
-
Existing settings:
- Does
.claude/settings.jsonexist? - Does
~/.claude/settings.jsonexist (global)? - Is there already a
__settings.jsoncfile?
- Does
-
Hook system:
- Is there a
lefthook.ymlorlefthook.yaml? - Is there a
.husky/directory? - For chezmoi: hooks aren't needed (uses run_onchange_)
- Is there a
-
Project structure:
- What's the scripts directory pattern? (scripts/, bin/, etc.)
- Is there a
package.json?
Use ls, Glob, and Read to explore. Example commands:
ls -la
ls -la .claude/ 2>/dev/null || echo "No .claude directory"
Step 2: Determine Configuration
Based on your analysis, determine the appropriate flags:
For regular projects:
--source .claude/__settings.jsonc--target .claude/settings.json--hook-system lefthook(orhuskyif.husky/exists)--scripts-path scripts/claude
For chezmoi dotfiles:
--source dot_claude/__settings.jsonc--target dot_claude/settings.json--hook-system chezmoi--install-global(optional, installs settings-manager to PATH)
For stow dotfiles:
--source <package>/__settings.jsonc(e.g.,claude/__settings.jsonc)--target <package>/settings.json--hook-system lefthook--scripts-path <package>/scripts
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.
- 24d ago Changed 63441637dc33
- 1mo ago Changed · -3 lines b1e7ce8f0644
- 1mo ago First seen · 195 lines · 9 tokens per session scan B 2303d7da98bb
settings-setup is a command published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 9 tokens to every session and 1,365 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
context
A project-context command that manages a .context directory containing decision notes, session logs, and history. It helps keep a record of why changes were made across Git branches and commits.
spec-research
A requirements-research command that turns a request into a set of constraints and checkable success criteria. It explores the relevant parts of a project in parallel and creates a structured proposal.
triage
Triage Linear issue with comprehensive analysis.
land
Resolve and squash merge one named, currently authorized pull request.
sync
Manually trigger plan-sync to update downstream task specs after implementation drift.
slack-gif-creator
Toolkit for creating animated GIFs optimized for Slack, with validators for size constraints and composable animation primitives. This skill applies when users request animated GIFs or emoji animations for Slack from descriptions like "make me a GIF for Slack of X doing Y".