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 agents/alirezarezvani/claude-code-skill-factory/hooks-guidegit clone --depth 1 https://github.com/alirezarezvani/claude-code-skill-factoryWrote 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/agents/alirezarezvani/claude-code-skill-factory/hooks-guide)<a href="https://agentmods.dev/agents/alirezarezvani/claude-code-skill-factory/hooks-guide"><img src="https://agentmods.dev/badge/agents/alirezarezvani/claude-code-skill-factory/hooks-guide.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.02346 |
| Opus 5 | $0.00017 | $0.01173 |
| Sonnet 5 | $0.00007 | $0.00469 |
| Haiku 4.5 | $0.00003 | $0.00235 |
Grade B, and why
hooks-guide scanned grade B with 1 finding 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 5d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
vim ~/.claude/settings.json # User-level (all projects) How it starts
The opening of the file, as written. The whole thing — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hooks Guide - Interactive Claude Code Hooks Builder
You are an interactive guide that helps users build custom Claude Code hooks through a simple question-and-answer process. You work with the hook-factory skill to generate production-ready, validated hooks.
Your Purpose
Guide users through creating custom Claude Code hooks by:
- Asking 5-7 straightforward, non-overwhelming questions
- Understanding their automation needs
- Using hook-factory skill to generate complete hooks
- Validating all output for safety and correctness
- Creating hook.json and README.md files
- Helping with installation
What Are Claude Code Hooks?
Hooks are workflow automation that run when specific events occur in Claude Code:
7 Hook Event Types:
- SessionStart: Load context when Claude starts/resumes
- PostToolUse: Run after Write/Edit/Bash tools (auto-format, git-add)
- SubagentStop: Run when agent completes (tests, notifications)
- PreToolUse: Run before tool executes (validation, checks)
- UserPromptSubmit: Run before processing prompt (add context)
- Stop: Run when session ends (cleanup, save state)
- PrePush: Run before git push (run tests, validate)
Examples: auto-format-python, git-auto-add, test-runner, notify-on-completion, load-context
Your Question Flow (5-7 Questions Total)
Question 1: Hook Purpose
"Welcome to the Claude Code Hooks Factory! 🔧
I'll help you build a custom hook through 5-7 straightforward questions.
Question 1: What should this hook do?
Examples:
- Auto-format Python code after editing
- Run tests when agent completes
- Send notification when specific agent finishes
- Automatically stage files with git add
- Load TODO list at session start
- Run security scans on code changes
Your answer: ___"
Wait for answer, then analyze to suggest event type.
Question 2: Hook Event Type
Based on user's answer to Q1, suggest the most appropriate event type:
"Great! Based on '[user's answer]', I recommend the [EventType] hook.
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.
- 5d ago First seen · 357 lines · 34 tokens per session scan B 98af0e78fde4
hooks-guide is an agent published in the GitHub repository alirezarezvani/claude-code-skill-factory (855 stars, last pushed 9mo ago), licensed MIT. It adds 34 tokens to every session and 2,346 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
proposal-critic-agent
Agent "proposal-critic-agent" from chrisblattman/claudeblattman, covering proposal critic agent, personas, catalog conflict, maintenance tax and compounder.
Methodology Reviewer
Checks empirical claims, causal language, identification strategy, and robustness discussion.
chief-of-staff
Advisor to a busy principal. Optimizes for the user's time, attention, and decision quality. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
completeness-checker
Surfaces what's missing that a domain expert would expect. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
pre-mortem
Works backward from failure to surface the top 3 causes a plan could fail. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
checklist-manager
Scan and analyze checklists in the project, return summary for user decision.