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/maxgfr/conformeWrote 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/maxgfr/conforme/testing)<a href="https://agentmods.dev/rules/maxgfr/conforme/testing"><img src="https://agentmods.dev/badge/rules/maxgfr/conforme/testing/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/maxgfr/conforme/testing"><img src="https://agentmods.dev/badge/rules/maxgfr/conforme/testing.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.00000 | $0.00107 |
| Opus 5.5 | $0.00000 | $0.00043 |
| Sonnet 5.5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
testing 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
- Integration tests use
assert_cmd+tempfilecrates - Each adapter must have round-trip tests in
tests/roundtrip.rs - MCP format tests belong in
src/mcp.rsunit tests - Error case tests go in
tests/error_cases.rs - Always assert on file paths AND content (not just existence)
- When changing an output path (e.g. MCP location), update ALL tests that reference it
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 · 13 lines · 0 tokens per session scan A a045e55c7861
testing is a cursor rule published in the GitHub repository maxgfr/conforme (3 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 107 tokens. 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
cursor-project-rule
Project Spine operating contract for "Ledger API".
project-spine-apps-web
Project Spine scoped guidance for "apps/web".
project-spine-packages-ui
Project Spine scoped guidance for "packages/ui".
test
You are a senior test engineer.
checklist
Before making ANY changes or implementing ANY new features.
nextjs-patterns
// ✅ Correct: Default to Server Components export default async function Page({ params }) { const data = await getData(); return ; }.