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/fmflurry/settings-opencodeWrote 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/fmflurry/settings-opencode/hooks)<a href="https://agentmods.dev/rules/fmflurry/settings-opencode/hooks"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/hooks/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/fmflurry/settings-opencode/hooks"><img src="https://agentmods.dev/badge/rules/fmflurry/settings-opencode/hooks.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.00198 | $0.00198 |
| Opus 5.5 | $0.00079 | $0.00079 |
| Sonnet 5.5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade B, and why
hooks 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 8d 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.
- Configure `permissions.allow` / `permissions.deny` in `~/.claude/settings.json` or project `.claude/settings.json` What it actually says
Hooks System
Hook Types
- PreToolUse: Before tool execution (validation, parameter modification)
- PostToolUse: After tool execution (auto-format, checks)
- Stop: When session ends (final verification)
Auto-Accept Permissions
Use with caution:
- Enable for trusted, well-defined plans
- Disable for exploratory work
- Never use dangerously-skip-permissions flag
- Configure
permissions.allow/permissions.denyin~/.claude/settings.jsonor project.claude/settings.json
TodoWrite Best Practices
Use TodoWrite tool to:
- Track progress on multi-step tasks
- Verify understanding of instructions
- Enable real-time steering
- Show granular implementation steps
Todo list reveals:
- Out of order steps
- Missing items
- Extra unnecessary items
- Wrong granularity
- Misinterpreted requirements
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.
- 8d ago First seen · 35 lines · 198 tokens per session scan B 4af5d486b4f1
hooks is a cursor rule published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 198 tokens to every session, about $0.0008 per session on Opus 5.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-10-08.
Other cursor rules, from other repositories
explorer-interface-brief
Use when asked to design the interface for an interactive 3D explorer, plan a UI for exploring a 3D model of a topic, or write an image-model prompt for a 3D learning app mock-up. Produces, from a topic, the UI design brief (audience, layout, panels, interactions, label style, colour palette, accessibility) and an…
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
simplicity
Simplicity - smallest correct diff; reuse, platform, installed deps before new code; no speculative abstraction.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
kiss-ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.