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/sifxprime/kodelyth-ecc/hookifygit clone --depth 1 https://github.com/sifxprime/kodelyth-eccWrote 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/sifxprime/kodelyth-ecc/hookify)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/hookify"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/hookify.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.00012 | $0.00266 |
| Opus 5 | $0.00006 | $0.00133 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
hookify 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
88% identical to hookify — 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
Create hook rules to prevent unwanted Claude Code behaviors by analyzing conversation patterns or explicit user instructions.
Usage
/hookify [description of behavior to prevent]
If no arguments are provided, analyze the current conversation to find behaviors worth preventing.
Workflow
Step 1: Gather Behavior Info
- With arguments: parse the user's description of the unwanted behavior
- Without arguments: use the
conversation-analyzeragent to find:- explicit corrections
- frustrated reactions to repeated mistakes
- reverted changes
- repeated similar issues
Step 2: Present Findings
Show the user:
- behavior description
- proposed event type
- proposed pattern or matcher
- proposed action
Step 3: Generate Rule Files
For each approved rule, create a file at .claude/hookify.{name}.local.md:
---
name: rule-name
enabled: true
event: bash|file|stop|prompt|all
action: block|warn
pattern: "regex pattern"
---
Message shown when rule triggers.
Step 4: Confirm
Report created rules and how to manage them with /hookify-list and /hookify-configure.
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 · 51 lines · 12 tokens per session scan A 2fd94b585a12
hookify is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 3d ago), licensed MIT. It adds 12 tokens to every session and 266 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to hookify, differing in 4 lines, and is treated as a copy.
Other commands, from other repositories
toh-help
Display all Toh Framework commands and quick usage guide.
opsx-new
Start a new change using the experimental artifact workflow (OPSX).
research
Delegate a thorough research investigation to the agy:runner subagent.
experiment
Design A/B test with statistical rigor. Usage: /mindforge:experiment [feature] [--metric conversion|engagement|revenue] [--duration 2w].
kimi-setup
Run node "$HOME/.kimi-plugin/kimi-companion.mjs" setup, then report installation and authentication status.
strategy-cfo
商业战略与财商融合决策专家 — 商业模式 / 资本结构 / 投资决策 / 资源配置 / 估值视角.