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/bookedsolidtech/discord-opsWrote 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/bookedsolidtech/discord-ops/002-verify-before-act)<a href="https://agentmods.dev/rules/bookedsolidtech/discord-ops/002-verify-before-act"><img src="https://agentmods.dev/badge/rules/bookedsolidtech/discord-ops/002-verify-before-act/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/bookedsolidtech/discord-ops/002-verify-before-act"><img src="https://agentmods.dev/badge/rules/bookedsolidtech/discord-ops/002-verify-before-act.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.00306 | $0.00306 |
| Opus 5.5 | $0.00122 | $0.00122 |
| Sonnet 5.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 2mo 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.
This is a copy
100% identical to 002-verify-before-act — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2mo 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/discord-ops (4 stars, last pushed 3mo ago), licensed MIT. It adds 306 tokens to every session, about $0.0012 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to 002-verify-before-act, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
selectools-providers
Rules for working with LLM provider adapters in selectools.
facebook-ads
Meta Ads (Facebook & Instagram) platform expertise. Audit campaigns, audiences, creative strategy, pixel tracking, and CAPI. Use when the user asks about Facebook Ads, Instagram Ads, Meta Ads, social media advertising, Advantage+ campaigns, or Meta pixel/CAPI setup.
skill-rails-api
Padrões DARE para APIs em Ruby on Rails 8 — API mode, ActiveRecord, Solid Queue, Solid Cable, Action Cable, strong parameters, services, serializers (Blueprinter/Alba), Devise/JWT, rack-attack, rswag/grape-swagger.
supreme-content-craft
Principal content craft for SEO/SEM/Header Binding/Copywriting/Marketing/Writing with six persuasion frameworks (AIDA, Cialdini, StoryBrand/PAS/FAB/Schwartz/SUCCESs/Ogilvy/Hopkins, Schopenhauer ethical eristic, Joe Girard Law of 250, Cialdini Pre-Suasion), Features to Project to How to Benefits to Sales to Purchase…
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.