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.
git clone --depth 1 https://github.com/waleedkhanbaloch/claude-code-safety-netWrote 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/waleedkhanbaloch/claude-code-safety-net/verify-custom-rules)<a href="https://agentmods.dev/commands/waleedkhanbaloch/claude-code-safety-net/verify-custom-rules"><img src="https://agentmods.dev/badge/commands/waleedkhanbaloch/claude-code-safety-net/verify-custom-rules/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/waleedkhanbaloch/claude-code-safety-net/verify-custom-rules"><img src="https://agentmods.dev/badge/commands/waleedkhanbaloch/claude-code-safety-net/verify-custom-rules.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.00006 | $0.00136 |
| Opus 5.5 | $0.00002 | $0.00054 |
| Sonnet 5.5 | $0.00001 | $0.00027 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
verify-custom-rules 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 2mo 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.
What it actually says
You are helping the user verify the custom rules config file.
Your Task
Run npx -y cc-safety-net --verify-config to check current validation status
If the config has validation errors:
- Show the specific validation errors
- Run
npx -y cc-safety-net --custom-rules-docto read the schema documentation - Use AskUserQuestion tool to offer fixes with your best suggestions
- After fixing, run
npx -y cc-safety-net --verify-configto verify again
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.
- 2mo ago First seen · 16 lines · 6 tokens per session scan A e64062b90be3
verify-custom-rules is a command published in the GitHub repository waleedkhanbaloch/claude-code-safety-net (2 stars, last pushed 19d ago), licensed MIT. It adds 6 tokens to every session and 136 once invoked, about $0.0000 per session on Opus 5.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-31.
Other commands, from other repositories
orchestrate
This tool coordinates Claude Code's actions. It does NOT write code or create content.
agentlas-local
Staff a task only from Agentlas agents registered on this machine.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
performance-bottlenecks
Identify and resolve performance bottlenecks in your development workflow.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.