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.
git clone --depth 1 https://github.com/ccashwell/evm-cortexWrote 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/rules/ccashwell/evm-cortex/hook-development)<a href="https://agentmods.dev/rules/ccashwell/evm-cortex/hook-development"><img src="https://agentmods.dev/badge/rules/ccashwell/evm-cortex/hook-development/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ccashwell/evm-cortex/hook-development"><img src="https://agentmods.dev/badge/rules/ccashwell/evm-cortex/hook-development.svg" alt="Reviewed on agentmods" width="80" 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.00264 | $0.00264 |
| Opus 5.5 | $0.00106 | $0.00106 |
| Sonnet 5.5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
hook-development 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 1mo 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
Hook Development Rules
Hook Architecture
Hooks are TypeScript files compiled to ESM bundles (.mjs) via esbuild.
Source: hooks/src/*.ts
Built: hooks/dist/*.mjs
Shared: hooks/src/shared/*.ts
When to Create Hooks
Hooks automate actions around agent events:
- Pre/post edit actions (run forge build, slither)
- Session lifecycle (start, end, compact)
- Memory and learning operations
- Security scanning (credential detection, SAST)
EVM-Specific Hook Patterns
forge-compile-check: Runforge buildafter .sol file editsslither-on-save: Run Slither after Solidity changesgas-snapshot-diff: Compare forge snapshots after editsnatspec-enforcer: Check NatSpec on public/external functionsstorage-layout-check: Validate storage layout for proxy contracts
Quality Rules
- Hooks must be fast (< 5 second execution)
- Never block on long-running operations
- Handle errors gracefully (log and continue)
- Keep hooks focused on one responsibility
- Use shared utilities from
hooks/src/shared/
Build
cd hooks && npm run build
Consider these rules if they affect your 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.
- 1mo ago First seen · 39 lines · 264 tokens per session scan A 7326c6896bd4
hook-development is a cursor rule published in the GitHub repository ccashwell/evm-cortex (131 stars, last pushed 17d ago), licensed MIT. It adds 264 tokens to every session, about $0.0011 per session on Opus 5.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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.