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/FeatureFactory-io/mimirWrote 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/featurefactory-io/mimir/do-continuous-testing)<a href="https://agentmods.dev/rules/featurefactory-io/mimir/do-continuous-testing"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-continuous-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/featurefactory-io/mimir/do-continuous-testing"><img src="https://agentmods.dev/badge/rules/featurefactory-io/mimir/do-continuous-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.00426 | $0.00426 |
| Opus 5.5 | $0.00170 | $0.00170 |
| Sonnet 5.5 | $0.00085 | $0.00085 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
do-continuous-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
Rule: Continuous Testing and Error Monitoring
Requirements
-
All tests must be runnable via
pytest tests/- Ensure pytest compatibility for all test files
- Use pytest fixtures and conventions
- Maintain Django test compatibility where needed
-
Tests must add their output to
tests.log- Configure pytest logging to write to
tests.log - Include detailed test results, errors, and timing
- Preserve log history for analysis
- Configure pytest logging to write to
-
Run tests continuously
- Monitor file changes and auto-run tests for the new and/or affected scenarios
- Use watch mode or interval-based execution
- Provide real-time feedback on test status
-
Monitor and fix errors automatically
- Parse test output and
tests.logfor failures - Identify root causes of test failures
- Implement fixes proactively
- Re-run tests to validate fixes
- Parse test output and
Implementation
Pytest Configuration
- Configure
pytest.iniorpyproject.tomlfor logging - Set up proper test discovery patterns
- Configure Django settings for pytest
Continuous Monitoring
- Use file watchers (e.g.,
pytest-watch,entr) - Parse test results in real-time
- Log analysis for error patterns
Error Fixing Protocol
- Categorize errors (syntax, logic, dependency, etc.)
- Apply appropriate fixes based on error type
- Formulate the target state (what should be the result of the fix)
- Inform user that you found the error, how you see target state, and what you are going to do to fix it
- Apply the fix
- Validate fixes with immediate test re-run
- Update tests if requirements have changed
Usage
When working on any codebase:
- Ensure pytest setup is complete
- Check background processes. If there is no continuous_test_runner.py - start it
- Do continuous test output monitoring
- Also monitor
tests.logfor issues - Fix errors as they are detected
- Maintain test health continuously
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 Changed · -4 lines · -7 tokens per session f7622d775e72
- 1mo ago First seen · 60 lines · 433 tokens per session scan A 7db0f8f74917
do-continuous-testing is a cursor rule published in the GitHub repository FeatureFactory-io/mimir (16 stars, last pushed 18d ago), licensed Apache-2.0. It adds 426 tokens to every session, about $0.0017 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-30.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
common-fixes
Utility for VAN QA common validation fixes.