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/incremental-validation)<a href="https://agentmods.dev/rules/rethunk-ai/clodbridge/incremental-validation"><img src="https://agentmods.dev/badge/rules/rethunk-ai/clodbridge/incremental-validation/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/incremental-validation"><img src="https://agentmods.dev/badge/rules/rethunk-ai/clodbridge/incremental-validation.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.00332 | $0.00332 |
| Opus 5.5 | $0.00133 | $0.00133 |
| Sonnet 5.5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
incremental-validation 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
Incremental Validation
Validate after each small increment, not after an entire subsystem.
Validation Frequency
| Milestone | Do It? | How |
|---|---|---|
| After 1 file (< 100 LOC) | Optional | Read for syntax |
| After 2-3 files (100-300 LOC) | YES | tsc --noEmit |
| After finishing a commit | YES | npm test |
| Before committing | YES | Both checks |
| After a subsystem | YES | Integration check |
Validation Checklist
Before moving to the next feature:
- TypeScript compiles (zero errors)
- No syntax errors
- Tests pass (if written)
- Imports resolve
- No unused variables
Error Cascade Prevention
Bad: Write 5 files → validate → 47 errors → debug for an hour
Good: Write 1 file → validate ✓ → Write 1 file → validate ✓ → Each step fast, errors caught immediately
When Validation Fails
Fix the issue, don't work around it:
- Type error? Fix the code or types
- Test failure? Debug and fix
- Import error? Find the missing file or wrong path
- Syntax error? Fix the typo
Re-validate after each fix.
For detailed validation strategies and error handling, see the incremental-validation 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 · 49 lines · 332 tokens per session scan A a867dd4c0a43
incremental-validation is a cursor rule published in the GitHub repository Rethunk-AI/clodbridge (0 stars, last pushed 3mo ago), licensed MIT. It adds 332 tokens to every session, about $0.0013 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
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
execute-test
Execute Katalon True Platform/TestOps tests when the input is an existing test case, manual test case list, test suite, suite collection, execution request, or "run with AI" instruction. Use when you need to create a manual test run, start Run with AI, poll AI session results, schedule automated suites, read…
roslyn-mcp-pitfalls
Known pitfalls and regression lessons from production use.
get-started
First-run onboarding for Katalon True Platform right after the Katalon connection is installed. Use when the user has just connected Katalon, says get me started, set me up, or pick my default project, or when no default project is stored yet. Confirms who is signed in, asks at most two questions to choose the default…
roslyn-mcp-version-bump
Auto-bump Version after successful MCP self-build and reload.
verification-before-completion
Require fresh, scope-appropriate evidence before any completion claim. Distinguishes implemented, locally verified, repository-green, PR-green, deployed, and observed-stable states.