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/ajsai47/holyclaude/helpgit clone --depth 1 https://github.com/ajsai47/holyclaudeWrote 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/ajsai47/holyclaude/help)<a href="https://agentmods.dev/commands/ajsai47/holyclaude/help"><img src="https://agentmods.dev/badge/commands/ajsai47/holyclaude/help.svg" alt="Measured on agentmods" 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 | $0.00007 | $0.01171 |
| Opus 5 | $0.00003 | $0.00585 |
| Sonnet 5 | $0.00001 | $0.00234 |
| Haiku 4.5 | $0.00001 | $0.00117 |
Grade D, and why
help scanned grade D with 2 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 3d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
Don't use chmod 777 - it's a security risk. Use specific permissions instead. Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- `rm\s+-rf` - matches "rm -rf" How it starts
The opening of the file, as written. The whole thing — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hookify Plugin Help
Explain how the hookify plugin works and how to use it.
Overview
The hookify plugin makes it easy to create custom hooks that prevent unwanted behaviors. Instead of editing hooks.json files, users create simple markdown configuration files that define patterns to watch for.
How It Works
1. Hook System
Hookify installs generic hooks that run on these events:
- PreToolUse: Before any tool executes (Bash, Edit, Write, etc.)
- PostToolUse: After a tool executes
- Stop: When Claude wants to stop working
- UserPromptSubmit: When user submits a prompt
These hooks read configuration files from .claude/hookify.*.local.md and check if any rules match the current operation.
2. Configuration Files
Users create rules in .claude/hookify.{rule-name}.local.md files:
---
name: warn-dangerous-rm
enabled: true
event: bash
pattern: rm\s+-rf
---
⚠️ **Dangerous rm command detected!**
This command could delete important files. Please verify the path.
Key fields:
name: Unique identifier for the ruleenabled: true/false to activate/deactivateevent: bash, file, stop, prompt, or allpattern: Regex pattern to match
The message body is what Claude sees when the rule triggers.
3. Creating Rules
Option A: Use /hookify command
/hookify Don't use console.log in production files
This analyzes your request and creates the appropriate rule file.
Option B: Create manually
Create .claude/hookify.my-rule.local.md with the format above.
Option C: Analyze conversation
/hookify
Without arguments, hookify analyzes recent conversation to find behaviors you want to prevent.
Available Commands
/hookify- Create hooks from conversation analysis or explicit instructions/hookify:help- Show this help (what you're reading now)/hookify:list- List all configured hooks/hookify:configure- Enable/disable existing hooks interactively
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.
- 3d ago First seen · 176 lines · 7 tokens per session scan D 39529a6e6473
help is a command published in the GitHub repository ajsai47/holyclaude (11 stars, last pushed 5mo ago), licensed MIT. It adds 7 tokens to every session and 1,171 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.