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/floriscornel/todo-mcp/testing-standardsgit clone --depth 1 https://github.com/floriscornel/todo-mcpWrote 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/floriscornel/todo-mcp/testing-standards)<a href="https://agentmods.dev/rules/floriscornel/todo-mcp/testing-standards"><img src="https://agentmods.dev/badge/rules/floriscornel/todo-mcp/testing-standards.svg" alt="Measured on agentmods" 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 | $0.00248 | $0.00248 |
| Opus 5 | $0.00124 | $0.00124 |
| Sonnet 5 | $0.00050 | $0.00050 |
| Haiku 4.5 | $0.00025 | $0.00025 |
Grade A, and why
testing-standards 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 5d 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
Testing Standards
Coverage Requirements
- Minimum 80% coverage for branches, functions, lines, and statements
- Use
npm run test:coverageto run tests with coverage reporting - Coverage reports available in
coverage/directory
Test Structure
- Follow the existing test patterns in
src/__tests__/ - Use Vitest with globals enabled
- Test database setup in
src/test-utils/vitest.setup.ts
Database Testing
- Use
TEST_DATABASE_URLenvironment variable for test database - Tests should be isolated and not affect each other
- Clean up test data after each test
Test Naming
- Describe what the test does:
should create task with valid data - Group related tests with
describeblocks - Use
beforeEach/afterEachfor setup/cleanup
Mock Patterns
- Mock external dependencies consistently
- Use Vitest's built-in mocking capabilities
- Avoid mocking internal functions unless necessary
Test Data
- Create meaningful test data that represents real usage
- Use factories or builders for complex test objects
- Keep test data minimal but realistic
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.
- 5d ago First seen · 37 lines · 248 tokens per session scan A bb487932bea5
testing-standards is a cursor rule published in the GitHub repository floriscornel/todo-mcp (2 stars, last pushed 6mo ago), licensed MIT. It adds 248 tokens to every session, about $0.0012 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
cursorrules
When the user asks about nist rmf, use nist-rmf-ai-mcp tools: assessriskprofile, mapaiimpact, generateriskcontrols, crosswalktoeuaiact, createriskreport.
cursorrules
When the user asks about quiz generator, use quiz-generator-ai-mcp tools: generatequiz, validateanswers, generateflashcards, assessdifficulty.
cursorrules
When the user asks about social media, use social-media-ai-mcp tools: schedulepost, generatehashtags, analyzeengagement, plancontentcalendar, getaudienceinsights.
cursorrules
When the user asks about web research, use web-research-mcp tools: websearch, browsepage, extractarticle, researchtopic, getweather.
cursorrules
When the user asks about lead scoring, use lead-scoring-ai-mcp tools: scorelead, addlead, updateleadactivity, getleadscore, getallleads.
cursorrules
When the user asks about ecommerce, use ecommerce-ai-mcp tools: writeproductdescription, optimizepricing, summarizereviews, forecastinventory, generateseometa.