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/kumaran-is/claude-code-onboarding/hookifygit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/hookify)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/hookify"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/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 | $0.00034 | $0.00814 |
| Opus 5 | $0.00017 | $0.00407 |
| Sonnet 5 | $0.00007 | $0.00163 |
| Haiku 4.5 | $0.00003 | $0.00081 |
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 today.
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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hookify — Create Rule
Create a .claude/hookify.*.local.md rule file to prevent an unwanted behavior.
Rules are active immediately — no restart needed.
Rule File Format
---
name: warn-console-log # kebab-case, start with verb: warn/block/require
enabled: true
event: file # bash | file | stop | prompt | all
pattern: console\.log\( # Python regex matched against relevant field
action: warn # warn (show message) | block (deny the tool call)
---
Message shown to Claude when rule triggers. Use markdown.
Fields for event:
bash→ matches thecommandfield of Bash tool callsfile→ matchesnew_text/file_pathof Edit/Write/MultiEdit callsstop→ fires when Claude tries to stop; block to enforce checklistprompt→ fires on user_prompt before Claude reads itall→ fires on every tool call
Advanced: multiple conditions (all must match)
conditions:
- field: file_path
operator: regex_match
pattern: \.ts$
- field: new_text
operator: contains
pattern: console.log
Operators: regex_match contains equals not_contains starts_with ends_with
Step 1 — Identify the Behavior
If $ARGUMENTS is provided: use that description as the behavior to prevent.
If $ARGUMENTS is empty: scan recent conversation for:
- Explicit corrections ("don't do X", "stop doing Y", "I didn't ask for that")
- Repeated patterns the user had to revert
- Frustrated reactions
List up to 4 candidate behaviors.
Step 2 — Ask User to Confirm
Use AskUserQuestion:
- Q1: "Which behavior(s) should become a rule?" (multiSelect: true, list each candidate)
- Q2: For each selected — "Should this block the operation or just warn?"
- Option A:
warn— show message but allow it to proceed - Option B:
block— deny the tool call entirely
- Option A:
Step 3 — Infer Pattern
For each confirmed behavior:
- Determine
event(bash, file, stop, prompt) - Write a Python regex
patternfor the relevant field - Test pattern mentally: does it match the bad case? Does it avoid false positives?
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.
- today First seen · 96 lines · 0 tokens per session scan A f676feef5f40
hookify is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 814 once invoked, about $0.0002 per session on Opus 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-09-03.
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.