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/hookify-configuregit 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-configure)<a href="https://agentmods.dev/commands/sifxprime/kodelyth-ecc/hookify-configure"><img src="https://agentmods.dev/badge/commands/sifxprime/kodelyth-ecc/hookify-configure.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.00008 | $0.00093 |
| Opus 5 | $0.00004 | $0.00046 |
| Sonnet 5 | $0.00002 | $0.00019 |
| Haiku 4.5 | $0.00001 | $0.00009 |
Grade A, and why
hookify-configure 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
89% identical to hookify-configure — 2 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
Interactively enable or disable existing hookify rules.
Steps
- Find all
.claude/hookify.*.local.mdfiles - Read the current state of each rule
- Present the list with current enabled / disabled status
- Ask which rules to toggle
- Update the
enabled:field in the selected rule files - Confirm the changes
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 · 15 lines · 8 tokens per session scan A a059c23f885d
hookify-configure is a command published in the GitHub repository sifxprime/kodelyth-ecc (11 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 93 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to hookify-configure, differing in 2 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
商业战略与财商融合决策专家 — 商业模式 / 资本结构 / 投资决策 / 资源配置 / 估值视角.