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/Flomenco-Inc/flo-pluginWrote 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/flomenco-inc/flo-plugin/verify-before-done)<a href="https://agentmods.dev/rules/flomenco-inc/flo-plugin/verify-before-done"><img src="https://agentmods.dev/badge/rules/flomenco-inc/flo-plugin/verify-before-done/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/flomenco-inc/flo-plugin/verify-before-done"><img src="https://agentmods.dev/badge/rules/flomenco-inc/flo-plugin/verify-before-done.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.00358 | $0.00358 |
| Opus 5.5 | $0.00143 | $0.00143 |
| Sonnet 5.5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade B, and why
verify-before-done scanned grade B with 2 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.
Subtle steeringmediumPrompt injection
Instructions that bias recommendations or shape behaviour without the user noticing.
**Never tell the user something is "fixed", "done", or "working" without proof.** The proof must be an actual runtime verification, not a code review of your own changes. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" "https://dev.floapp.co/v1/oauth/google-drive/authorize-url" What it actually says
Verify Before Claiming Done
Never tell the user something is "fixed", "done", or "working" without proof. The proof must be an actual runtime verification, not a code review of your own changes.
The rule
Before any of these phrases (or equivalent):
- "This should now work"
- "The fix is ready"
- "Issue is resolved"
You MUST have at least one of the following:
For plugin code changes
Run the plugin locally and confirm it connects:
npm run build && npm start
# Verify: no startup errors, MCP handshake succeeds
For OAuth/auth changes
Test the actual OAuth flow against dev:
# Verify the authorize URL returns a redirect, not a 403/500
curl -s -o /dev/null -w "%{http_code}" "https://dev.floapp.co/v1/oauth/google-drive/authorize-url"
For API integration changes
Call the actual API endpoint the plugin uses:
curl -s -X GET "https://api.dev.floapp.co/v1/<endpoint>" \
-H "Authorization: Bearer $TOKEN" | jq .
What does NOT count as verification
- "I've reviewed the code and it looks correct"
- "The tests pass" (unit tests mock the API)
- "It compiled successfully"
When the user reports "still broken"
Before making another code change:
- Reproduce the exact failure
- Follow
root-cause-before-fix.mdcbefore writing code
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 · 54 lines · 358 tokens per session scan B f3926eadb566
verify-before-done is a cursor rule published in the GitHub repository Flomenco-Inc/flo-plugin (0 stars, last pushed 1mo ago), licensed MIT. It adds 358 tokens to every session, about $0.0014 per session on Opus 5.5. A static security scan graded it B with 2 findings (subtle steering, makes network calls). 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
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.