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/Rethunk-AI/clodbridgeWrote 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/rethunk-ai/clodbridge/solve-blockers-proactively)<a href="https://agentmods.dev/rules/rethunk-ai/clodbridge/solve-blockers-proactively"><img src="https://agentmods.dev/badge/rules/rethunk-ai/clodbridge/solve-blockers-proactively/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/rethunk-ai/clodbridge/solve-blockers-proactively"><img src="https://agentmods.dev/badge/rules/rethunk-ai/clodbridge/solve-blockers-proactively.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.00295 | $0.00295 |
| Opus 5.5 | $0.00118 | $0.00118 |
| Sonnet 5.5 | $0.00059 | $0.00059 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
solve-blockers-proactively 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
Solve Blockers Proactively
When you hit a blocker, don't ignore it. Either solve it or ask the user.
What's a Blocker
- Can't run tests (npm/bun install failed)
- Can't verify code compiles (tsc unavailable)
- A critical dependency isn't available
- A permission or filesystem error blocks progress
Decision Tree
Is there a workaround I can try in < 10 minutes?
- YES → Try it
- Worked? → Continue
- Failed? → Escalate
- NO → Escalate
Escalate means:
- Explain the blocker clearly
- Offer 2-3 options for the user
- Wait for guidance before proceeding
Examples
npm install fails (EROFS):
- Try
npm install --cache=/tmp/... - Try
bun install - If both fail: "npm and bun both hit sandbox restrictions. Options: (1) install deps outside Claude Code, (2) I validate code manually"
tsc not available:
- Try
npx tsc --noEmit - Try
bun run typecheck - If neither works: escalate
For detailed blocker resolution flowcharts and workarounds, see the solve-blockers-proactively 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.
- 1mo ago First seen · 46 lines · 295 tokens per session scan A 7350fd085e3c
solve-blockers-proactively is a cursor rule published in the GitHub repository Rethunk-AI/clodbridge (0 stars, last pushed 3mo ago), licensed MIT. It adds 295 tokens to every session, about $0.0012 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-31.
Other cursor rules, from other repositories
solution-exploration-guide
When examining how to implement an issue.
bootstrap-alwayson
Minimal always-required LLM fixes.
error-handling-and-validation
A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.
debugging
Debugging guidance for the Lineai MCP Server.
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.
roslyn-mcp-decompile
Assembly resolve, ILSpy decompile, NuGet/BCL fallback.