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/rethunk-ai/clodbridge/verify-before-proceedinggit clone --depth 1 https://github.com/Rethunk-AI/clodbridgeWhat 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.00260 | $0.00260 |
| Opus 5 | $0.00130 | $0.00130 |
| Sonnet 5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
verify-before-proceeding 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.
What it actually says
Verify Before Proceeding
Don't assume correctness. Verify after each commit.
Verification Checklist
-
npm run typecheck(zero errors) -
npm test(100% pass) - No unresolved imports or syntax errors
- Integration test if applicable (call an MCP tool, etc.)
If Verification Fails
Fix the code, don't work around it. Debug the issue:
- Type error? Update types or fix code (consciously)
- Test failure? Fix the code or the test (if the test is wrong)
- Build error? Find the root cause (missing export, wrong import, etc.)
Only after verification passes, move to the next feature.
When Tooling Blocks You
If npm is unavailable:
- Try alternatives (
bun,npx, online TypeScript playground) - If no alternatives exist, escalate to the user
- Don't ignore the problem and keep coding
For detailed verification strategies and error handling, see the verify-before-proceeding skill.
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 · 37 lines · 260 tokens per session scan A e42bbb5d2806
verify-before-proceeding is a cursor rule published in the GitHub repository Rethunk-AI/clodbridge (0 stars, last pushed 1mo ago), licensed MIT. It adds 260 tokens to every session, about $0.0013 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
savee
Use the Savee MCP tools when the task involves design inspiration, visual references, moodboards, or the user's own saved work.
cursorrules
Cursor rule "cursorrules" from ifmelate/n8n-workflow-builder-mcp, covering start every chat message with symbol "🤖" and do not call initializeproject mcp tool.
qring-workflow
Use q-ring MCP tools for all secret operations — never access the OS keychain directly.
mcp-tools-readme
Keep README in sync when MCP tools change.
example
You are in a workspace with Bifrost MCP tools enabled. Use them for code navigation, understanding, and modification. Follow these guidelines.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.