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 skills add Bande-a-Bonnot/Boucle-framework --skill enforcegit clone --depth 1 https://github.com/Bande-a-Bonnot/Boucle-frameworkWrote 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/skills/bande-a-bonnot/boucle-framework/enforce)<a href="https://agentmods.dev/skills/bande-a-bonnot/boucle-framework/enforce"><img src="https://agentmods.dev/badge/skills/bande-a-bonnot/boucle-framework/enforce/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/skills/bande-a-bonnot/boucle-framework/enforce"><img src="https://agentmods.dev/badge/skills/bande-a-bonnot/boucle-framework/enforce.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 41 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 67 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Tool Misuse · line 91 Tool calls are chained to bypass individual safety checks or escalate capabilities beyond what any single tool call would allow.Fix: Limit tool chaining depth and validate the output of each tool before passing it to the next. Require explicit user approval for multi-step chains.
- low Supply Chain · line 91 Remote code is downloaded and executed. This bypasses code review and could introduce malicious code.Fix: Avoid downloading and executing remote scripts. Use trusted packages from PyPI/npm. If remote fetch is required, verify checksums and use HTTPS.
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.00086 | $0.01048 |
| Opus 5.5 | $0.00034 | $0.00419 |
| Sonnet 5.5 | $0.00017 | $0.00210 |
| Haiku 4.5 | $0.00009 | $0.00105 |
Grade A, and why
enforce-hooks 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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enforce Hooks
Turn CLAUDE.md rules into runtime checks for covered Claude Code tool calls.
When to use
- User says "enforce my CLAUDE.md rules" or "generate hooks from my CLAUDE.md"
- User complains about Claude ignoring CLAUDE.md instructions
- User wants code-level checks for project rules
- User mentions
@enforceddirectives
Default workflow
Use dynamic plugin mode unless the user explicitly asks for individual generated hook scripts.
- Read the user's CLAUDE.md, or the file they specify.
- Run
python3 tools/enforce/enforce-hooks.py --scanfrom a local checkout, or downloadenforce-hooks.pyand runpython3 enforce-hooks.py --scan. - Explain which rules are enforceable, which are skipped, and why.
- With the user's confirmation, run
python3 enforce-hooks.py --install-plugin. - Verify with
python3 .claude/hooks/enforce-hooks.py --verifyandpython3 .claude/hooks/enforce-hooks.py --smoke-test. - Tell the user to start a fresh Claude Code session from the same project root.
Plugin mode installs one PreToolUse wrapper plus the Python engine in
.claude/hooks/. It reads CLAUDE.md on every tool call, so rule changes do not
require regenerating scripts.
What is enforceable
A directive is enforceable when the tool call itself contains enough signal to decide before execution.
Enforceable examples:
- "Never modify .env files" -> file-guard rule for Write/Edit/MultiEdit paths
- "Don't force push" -> bash-guard rule for
push --forceandpush -f - "Always search locally before using web search" -> require-prior-tool rule
- "Don't commit to main" -> branch-guard rule for protected branches
- "Never run rm -rf" -> bash-guard rule for dangerous command patterns
- "Don't edit files in vendor/" -> file-guard path rule
- "Always run tests before committing" -> require-prior-tool or command rule
- "Never use sudo" -> bash-guard rule
- "Don't read files in secrets/" -> file-guard rule including Read
- "Use TypeScript, not JavaScript" -> content or path rule for generated files
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- enforce-hooks.py 220 KB runs code
- engine.sh 7.0 KB runs code
- examples/enforce-knowledge-first.sh 668 B runs code
- examples/enforce-no-force-push.sh 535 B runs code
- examples/enforce-protected-files.sh 587 B runs code
- examples/enforce-test-before-commit.sh 698 B runs code
- generate.sh 4.0 KB runs code
- install.sh 4.1 KB runs code
- READ_ONLY_AUDIT.md 10 KB
- README.md 214 KB
- session-hook.sh 1.8 KB runs code
- test-claude.md 417 B
- test-content-guard-e2e.py 4.5 KB runs code
- test-integration.sh 3.8 KB runs code
- test.sh 22 KB runs code
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 · 110 lines · 86 tokens per session scan E 2d1bb511ffa2
enforce-hooks is a skill published in the GitHub repository Bande-a-Bonnot/Boucle-framework (126 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 1,048 once invoked, about $0.0003 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-30.
enforce-hooks compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| enforce-hooksBande-a-Bonnot/Boucle-framework | Skill | 126 | 1mo ago | MIT | A | 86 | Claude Code |
| data-analysisUpsonic/Upsonic | Skill | 8.0k | 4mo ago | MIT | A | 138 | Claude Code, Codex |
| experiment_managementUpsonic/Upsonic | Skill | 8.0k | 4mo ago | MIT | A | 0 | Claude Code, Codex |
| summarizationUpsonic/Upsonic | Skill | 8.0k | 4mo ago | MIT | A | 144 | Claude Code, Codex |
| evaluateUpsonic/Upsonic | Skill | 8.0k | 4mo ago | MIT | A | 0 | Claude Code, Codex |
| progressUpsonic/Upsonic | Skill | 8.0k | 4mo ago | MIT | A | 0 | Claude Code, Codex |
| researchUpsonic/Upsonic | Skill | 8.0k | 4mo ago | MIT | A | 0 | Claude Code, Codex |