cc safe setup
- Repo stars 29
- Author repo cc-safe-setup
- Domain
- Security
- Author-declared agents
- No explicit declaration found; this is not inferred or tested compatibility
- Static check
- 88 / 100 · heuristic scan, not runtime safety proof
- Runtime evidence
- Not run; no isolated runtime test evidence is currently recorded
- Author / version / license
- @yurukusa · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- macOS · Linux · Windows
- Runtime requirements
- No explicit requirements detected
- Detected file/system behavior
-
- Read-only
- Shell exec
- Env read
- Network behavior
- Local-only
- Install commands
- None (reference only)
Heads up: Tool permissions are not declared; actual access depends on the runtime.
# cc-safe-setup
Safety-first configuration for Claude Code. Prevents the accidents that happen when AI writes code autonomously.
## What it does
Installs pre-built safety hooks into your Claude Code environment. These hooks run automatically before/after tool calls to block dangerous operations.
**Categories:**
- **File protection**: Block `rm -rf`, prevent overwriting files outside project
- **Git safety**: Prevent force-push to main, block `reset --hard`
- **Credential guards**: Stop `.env` files from being committed or read by AI
- **Token optimization**: Warn on large file reads, limit subagent spawning
- **Quality gates**: Detect lazy rewrites, verify claims before committing
## Quick start
```bash
npx cc-safe-setup
```
This runs an interactive wizard that configures hooks based on your risk profile.
## Install individual hooks
```bash
npx cc-safe-setup --install-example large-read-guard
npx cc-safe-setup --install-example prevent-rm-rf
npx cc-safe-setup --install-example git-force-push-block
```
## Why hooks instead of CLAUDE.md rules
Rules in CLAUDE.md are suggestions — Claude can forget them. Hooks are enforced at the system level. A hook that blocks `rm -rf` cannot be overridden by the AI.
From 800+ hours of autonomous operation: the hooks that matter most are the ones you don't notice until something goes wrong.
## Resources
- Repository: https://github.com/yurukusa/cc-safe-setup
- Hook Selector (find hooks for your setup): https://yurukusa.github.io/cc-safe-setup/hook-selector.html
- Token Checkup (diagnose waste): https://yurukusa.github.io/cc-safe-setup/token-checkup.html
Sections and files
Listed in source order.
sections -> What it does → Quick start → Install individual hooks → Why hooks instead of CLAUDE.md rules → Resources
terms -> Categories · File protection · Git safety · Credential guards · Token optimization · Quality gates
files/cmd -> rm -rf · reset --hard · .env · before/after · CLAUDE.md · github.com/yurukusa/cc-safe-setup · yurukusa.github.io/cc-safe-setup/hook-selector.html · yurukusa.github.io/cc-safe-setup/token-checkup.html
body sha256 -> b46f196ae6ac
What it does
Installs pre-built safety hooks into your Claude Code environment. These hooks run automatically before/after tool calls to block dangerous operations. Categories: File protection: Block
rm -rf, prevent overwriting files outside project Git safety: Prevent force-push to main, blockreset --hardCredential guards: Stop.envfiles from being committed or read by AIQuick start
This runs an interactive wizard that configures hooks based on your risk profile.
Why hooks instead of CLAUDE.md rules
Rules in CLAUDE.md are suggestions — Claude can forget them. Hooks are enforced at the system level. A hook that blocks
rm -rfcannot be overridden by the AI. From 800+ hours of autonomous operation: the hooks that matter most are the ones you don't notice until something goes wrong.Resources
Repository: https://github.com/yurukusa/cc-safe-setup Hook Selector (find hooks for your setup): https://yurukusa.github.io/cc-safe-setup/hook-selector.html Token Checkup (diagnose waste): https://yurukusa.github.io/cc-safe-setup/token-checkup.html