Claude Code: five settings rules and a five-check script for .claude/settings.json (free sample)
by PaperChaseWebb
From the Claude Code bundle: five rules for .claude/settings.json (bypass stays off and switched off, deny reading .env, allow named commands not whole tools, git push asks, hooks run scripts kept in the project), and a read-only script that checks one settings file for them.
- Price
- Free
- Difficulty
- Beginner
- Setup
- 5 min
- Format
- .md file
claude-code-five-settings-rules-and-a-five-check-script-free-sample.md · 7 KB · direct download, no signup
What you end up with
In a few minutes you can see whether your Claude Code settings let the agent read your keys, run anything, or push without asking.
What you get
- Five settings rules
- cc_mini.py: five read-only checks on one settings.json
- One prompt
- Worked example: 5 findings, then 0
Who it is for
Anyone on Claude Code who wants a quick check of their permissions file first.
Works with
Solid chips: the agent is named in this listing's own tools list. Dashed chip: Plain Markdown, so it also pastes into other agents such as Grok Bot, Hermes, OpenClaw or Muse. We list those as compatible by format only, not as tested.
Tools needed
Cost to run: Free.
Time to result: About five minutes to a first result
Sample prompts, free to use
Read .claude/settings.json and list every allow rule with what it lets you do. Mark any that are wider than the commands this project runs. Propose a narrower list and wait for my yes before changing the file.
The rules and the script are in the file.
Free preview of the file
# Claude Code: five settings rules and a five-check script for .claude/settings.json (free sample)
Version 1.0, 2026-10-29. By PaperChaseWebb. For developers who use Claude Code every day, alone or next to Codex, Hermes or Grok Bot. One Markdown file and one Python 3 script, standard library only. The script was tested on its worked example (5 findings, then 0) and on a missing file (exit 2). It reads one settings file; it was not run inside Claude Code or any other harness.
Most Claude Code setups that go wrong go wrong in the same file. Bypass mode is on because the prompts were annoying. .env is readable because nobody wrote a deny rule. Plain Bash is allowed because it was faster. git push happens without a question. A hook runs a script from someone's Downloads folder. This sample gives you the five rules that cover those, and a script that checks them in one settings.json.
## Install in one line
Save this page as FREE-SAMPLE.md, then:
```
python3 -c "import re;t=open('FREE-SAMPLE.md').read();open('cc_mini.py','w').write(re.search(r'~~~python\n(.*?)~~~',t,re.S).group(1))"
python3 cc_mini.py .claude/settings.json
```
## Five settings rules
1. **Bypass stays off, and stays switched off.** Never make bypassPermissions the default mode, and set disableBypassPermissionsMode to "disable" so nobody turns it on in a hurry.
2. **Deny reading your keys.** Read(./.env) and Read(./.env.*) go in deny, plus any folder where you keep secrets.
3. **Allow named commands, never whoTest record
- Date
- Oct 29, 2026
- What was run
- cc_mini.py on the worked example, a fixed file, a missing file, and the copy taken from the sample file.
- Result
- 5 findings, then 0; exit 2 on a missing file; the copy behaved the same.
- Not run
- Claude Code or any other harness.
Copied from this item's dated test notes. What was not run stays in.
Worth knowing
- The sample checks one settings file against five rules. The full Claude Code Setup Runbook, gate, request approvals by hash, source and vetting records and the fifteen checks are in the full bundle.
- On 2026-10-29 cc_mini.py gave 5 findings on the worked example, then 0 on the fixed file, and exited 2 on a missing file; the copy extracted from the sample file behaved the same. It was not run inside Claude Code or any other harness.
Questions
Does it send anything anywhere?
No. It reads one file and opens no network connection.
What is in the full bundle?
The Claude Code Setup Runbook with fifteen checks and owner approval tied to each request's hash, plus Agent Rules starter files, Agent Skills Workshop, MCP Setup Playbook and Vet Before You Install in full. $69, against $101 for the four bought separately.
Details
Version 1.0 · Updated Oct 29, 2026 · Markdown version of this page
License: Personal and commercial use. Download terms
Related
Claude Code bundle: four packs and a setup runbook a script checks before your agent touches anything risky
Agent Rules starter files, Agent Skills Workshop, MCP Setup Playbook and Vet Before You Install in full, tied into one checked Claude Code setup by a new Claude Code Setup Runbook. cc_check.py reads CLAUDE.md, .claude/settings.json, skills, subagents, hooks and .mcp.json and names fifteen kinds of problem: bypass mode left on, .env readable, blanket allows, git push that never asks, skills that cannot trigger, subagents with every tool, unpinned servers, keys in config, and third-party pieces nobody vetted. cc.py gates ten risky setup changes, and each waits for the owner's yes typed at their terminal and tied to that request's sha256.
Codex: five config rules and a five-check script for .codex/config.toml (free sample)
From the Codex bundle: five rules for .codex/config.toml (keep the sandbox on, approval on-request, network off by default, pin the model, pin servers and keep keys out), and a read-only script that checks one config file for them.
Vet Before You Install: twelve checks, a sandbox recipe and a tested vetting folder for third-party agent code
Decide whether a skill, plugin, mod, MCP server, connector, repo or model gets into your agent setup: sort the seat, read every file that runs, map reach and the data path, pin and vendor it, trial it in a sandbox with a planted fake key, then record a decision the owner approves at their own terminal. v1.1 adds a seat sort before any vetting, two new checks (data path and reach, approval surfaces), evidence tiers, twelve token classes including hidden text, encoded strings, startup file edits and approval hooks, a fresh-session second read, data path questions for proxies and routers, dependency and model weight pinning, a fifth decision (not vettable) with recheck dates and an approved shelf, more special cases, a vetting folder with a fifteen-check read-only checker and an owner approval helper, agent files for Grok Bot, Claude Code, Codex and Hermes, and twelve new prompts (27 in all). Price unchanged.
MCP server setup playbook: connect your agent to real tools without handing over the keys
Pick the fewest MCP servers for a job, check them before installing, scope the credentials, configure five clients, test with MCP Inspector and build a small read-only server of your own.