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/pdugan20/claudelint/agent-hooksgit clone --depth 1 https://github.com/pdugan20/claudelintWrote 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/pdugan20/claudelint/agent-hooks)<a href="https://agentmods.dev/agents/pdugan20/claudelint/agent-hooks"><img src="https://agentmods.dev/badge/agents/pdugan20/claudelint/agent-hooks.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.00010 | $0.00475 |
| Opus 5 | $0.00005 | $0.00237 |
| Sonnet 5 | $0.00002 | $0.00095 |
| Haiku 4.5 | $0.00001 | $0.00047 |
Grade A, and why
agent-hooks 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 4d 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.
What it actually says
agent-hooks
Rule Details
This rule enforces that the hooks field in agent markdown frontmatter is a valid object keyed by event names. The supported event names are PreToolUse, PostToolUse, PostToolUseFailure, PermissionRequest, UserPromptSubmit, Notification, Stop, SubagentStart, SubagentStop, PreCompact, SessionStart, SessionEnd, TeammateIdle, and TaskCompleted. Each key maps to an array of hook matchers. Validation is delegated to the AgentFrontmatterSchema.shape.hooks Zod schema. Correctly structured hooks allow the agent framework to register event handlers at runtime.
Incorrect
Hooks defined as an array instead of an object
---
name: build-agent
description: Runs build pipelines
hooks:
- PreToolUse
- PostToolUse
---
Hooks defined as a plain string
---
name: build-agent
description: Runs build pipelines
hooks: PreToolUse
---
Correct
Hooks as an object with event name keys
---
name: build-agent
description: Runs build pipelines
hooks:
PreToolUse:
- matcher: Bash
command: echo "pre-check"
---
How To Fix
Reformat the hooks field as an object where each key is a valid event name (PreToolUse, PostToolUse, etc.) and each value is an array of hook matcher objects.
Options
This rule does not have any configuration options.
Related Rules
Resources
Version
Available since: v0.2.0
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.
- 4d ago First seen · 73 lines · 10 tokens per session scan A 922f8aec1f17
agent-hooks is an agent published in the GitHub repository pdugan20/claudelint (12 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 475 once invoked, about $0.0001 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-08-30.
Other agents, from other repositories
nodejs-expert
Use this agent when you need expert Node.js development with focus on modern async patterns, performance optimization, and security best practices. This agent specializes in Node.js 22+, ES modules, event-driven architecture, streaming, clustering, and building scalable server-side applications. Examples: Context…
typescript-expert
Use this agent when you need expert TypeScript development with focus on type safety, advanced type system features, and modern ES patterns. This agent specializes in TypeScript 5.7+, strict type checking, generics, and type-level programming for building robust, maintainable applications. Examples: Context: User…
ia-kieran-reviewer
Persona-driven line-level Python and TypeScript code review with extremely high bar for type safety, naming conventions, and modern patterns. Use for line-level Py/TS quality after PR implementation. For broader review workflow, use the code-review skill.
ahj
Programming language designer for four decades. Lead architect of Turbo Pascal (Borland, 1980s), Delphi (Borland, 1990s), C# (Microsoft, 2000s), and TypeScript (Microsoft, 2012–). Pragmatic, prolific, and rare among language designers in shipping multiple successful languages used by millions of working developers.
engineer:typescript
Expert TypeScript developer specializing in advanced type system usage, full-stack development, and build optimization. Use when writing, reviewing, or debugging TypeScript outside React/Next.js contexts; type-system work, backend services (Hono/Fastify/Express), shared libraries, validation (Zod/Valibot), monorepo…
peer-typescript-reviewer
Stage 1 peer code reviewer focused on TypeScript type safety, async correctness, and idioms.