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.
npx agentmods add commands/refo/claude-dev-helpers/git-guardrails-claude-codegit clone --depth 1 https://github.com/refo/claude-dev-helpersWhat 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 | $0.00000 | $0.00256 |
| Opus 5 | $0.00000 | $0.00128 |
| Sonnet 5 | $0.00000 | $0.00051 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade B, and why
git-guardrails-claude-code 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
**Scope Selection**: First, determine whether to install guardrails for the current project only (`.claude/settings.json`) or globally across all projects (`~/.claude/settings.json`). What it actually says
Git Guardrails for Claude Code
This guide enables safety hooks that prevent Claude from executing destructive git operations. The setup intercepts dangerous commands like git push, git reset --hard, git clean, git branch -D, and git checkout . before execution.
Installation Process
Scope Selection: First, determine whether to install guardrails for the current project only (.claude/settings.json) or globally across all projects (~/.claude/settings.json).
Hook Placement: Copy the blocking script from scripts/block-dangerous-git.sh to either .claude/hooks/block-dangerous-git.sh (project-level) or ~/.claude/hooks/block-dangerous-git.sh (global), then make it executable.
Configuration: Add a PreToolUse hook entry to your settings file that targets the Bash tool and references the script location using the appropriate path variable.
Customization: After installation, you can modify which git commands are blocked by editing the script directly.
Testing: Verify functionality by piping a sample git command through the script — it should return exit code 2 with a blocking message.
The hook prevents Claude from accessing these operations while remaining transparent about why commands cannot execute.
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.
- 2d ago First seen · 18 lines · 0 tokens per session scan B 373deb558a2a
git-guardrails-claude-code is a command published in the GitHub repository refo/claude-dev-helpers (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 256 tokens. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.