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 rules/bookedsolidtech/helixir/002-verify-before-actgit clone --depth 1 https://github.com/bookedsolidtech/helixirWhat 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.00306 | $0.00306 |
| Opus 5 | $0.00153 | $0.00153 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
002-verify-before-act 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- 002-verify-before-act — 100% identical, 0 lines differ
What it actually says
Verify Before Acting
Read before writing. Verify before installing. Confirm before deleting.
Rules
-
Read before writing. Before editing a file, read the current version. Never overwrite without knowing what's there. Never assume file contents from memory.
-
Verify package existence before installing. Before running
npm install <pkg>,composer require <pkg>, or any equivalent, confirm the package exists and its name is spelled correctly. Use the package registry, not your training data. -
Confirm before destructive operations. Before
git reset,git clean, file deletion, or database drops — state what you're about to do and why. Wait for acknowledgement if there's any doubt. -
Check current state before declaring it. Before saying "the build passes" or "there are no TypeScript errors", run the check. Do not rely on previous results from earlier in the session.
-
Verify tool availability before use. Before running a CLI tool (docker, act, composer, drush, etc.), check that it's installed. Don't assume availability.
When to apply
- Before any write or edit operation
- Before any
install,add,require, orupdatecommand - Before any destructive git operation
- Before any claim about current system state
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.
- 2d ago First seen · 29 lines · 306 tokens per session scan A efdf7c79b95b
002-verify-before-act is a cursor rule published in the GitHub repository bookedsolidtech/helixir (5 stars, last pushed 2mo ago), licensed MIT. It adds 306 tokens to every session, about $0.0015 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-31.
Other cursor rules, from other repositories
ux-audit
UX audit and design guidance skill.
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-agent-orchestration
Cursor 3.7 orchestration guide: when to plan, when to delegate, nested subagents, multi-environment handoffs, /best-of-n, and Await for long-running branches.
solana-transaction-safety
Safe Solana transaction submission patterns using Helius Sender.
reqforge-dev-build
Dev Builder — implementation execution. Build code phase by phase following DEV-PLAN, each Task goes through review → fix loop.
cursor_rules
Flutter team guidelines for Cursor.