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/fmarzochi/egc/hookify-helpgit clone --depth 1 https://github.com/Fmarzochi/EGCWrote 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/fmarzochi/egc/hookify-help)<a href="https://agentmods.dev/commands/fmarzochi/egc/hookify-help"><img src="https://agentmods.dev/badge/commands/fmarzochi/egc/hookify-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.1 | $0.00007 | $0.00271 |
| Opus 5 | $0.00003 | $0.00135 |
| Sonnet 5 | $0.00001 | $0.00054 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
hookify-help 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 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.
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.
This is a copy
91% identical to hookify-help — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Display comprehensive hookify documentation.
Hook System Overview
Hookify creates rule files that integrate with Gemini Code's hook system to prevent unwanted behaviors.
Event Types
bash: triggers on Bash tool use and matches command patternsfile: triggers on Write/Edit tool use and matches file pathsstop: triggers when a session endsprompt: triggers on user message submission and matches input patternsall: triggers on all events
Rule File Format
Files are stored as .gemini/hookify.{name}.local.md:
---
name: descriptive-name
enabled: true
event: bash|file|stop|prompt|all
action: block|warn
pattern: "regex pattern to match"
---
Message to display when rule triggers.
Supports multiple lines.
Commands
/hookify [description]creates new rules and auto-analyzes the conversation when no description is given/hookify-listlists configured rules/hookify-configuretoggles rules on or off
Pattern Tips
- use regex syntax
- for
bash, match against the full command string - for
file, match against the file path - test patterns before deploying
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 · 47 lines · 7 tokens per session scan A ea616fb31159
hookify-help is a command published in the GitHub repository Fmarzochi/EGC (48 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 271 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to hookify-help, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
demand-discovery
Run automated niche demand discovery research across 7 data sources and 26 categories.
tdd-workflow
Implement the behavior described in $ARGUMENTS using strict TDD. Follow this exact sequence. Do not collapse phases. Each gate requires actual test runner output.
api-add-endpoint
Create a new API endpoint. $ARGUMENTS should describe the endpoint (e.g., "POST /api/users - create a user").
api-test-endpoint
Test the API endpoint specified in $ARGUMENTS.
code-review
Review the code changes in this project. For each file changed.
refactor-file
Refactor the file specified in $ARGUMENTS following project conventions.