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/featurefactory-io/mimir/do-continuous-testinggit clone --depth 1 https://github.com/FeatureFactory-io/mimirWhat 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.00433 | $0.00433 |
| Opus 5 | $0.00217 | $0.00217 |
| Sonnet 5 | $0.00087 | $0.00087 |
| 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 2d 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.
- 2d 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 (13 stars, last pushed 4d ago), licensed Apache-2.0. It adds 433 tokens to every session, about $0.0022 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-30.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.