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/davidl71/project-management-automation/testinggit clone --depth 1 https://github.com/davidl71/project-management-automationWhat 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.00000 | $0.00380 |
| Opus 5 | $0.00000 | $0.00190 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
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 yesterday.
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 Rules
Test Organization
File Structure
- One test file per tool/module:
project_management_automation/tools/automation_opportunities.py→tests/test_automation_opportunities.py - Dedicated files for shared utilities: Shared network utilities →
tests/test_utils_network.py - Avoid duplicate tests: Never duplicate the same test in multiple files
Naming Conventions
- Use descriptive test names:
test_find_automation_opportunities_success(nottest_success) - Include context in names to prevent duplicates across files
- Group related tests into test classes:
TestAutomationOpportunitiesTool
See: Test Organization Guidelines
Test Structure
- Use descriptive test names
- Follow Arrange-Act-Assert pattern
- One assertion per test when possible
- Group related tests into test classes
Mocking
- Mock external dependencies
- Use dependency injection for testability
- Reset mocks between tests
Coverage
- Aim for >80% code coverage
- Cover edge cases and error paths
- Test both happy and unhappy paths
Performance
- Keep tests fast (<1s each)
- Use fixtures for expensive setup
- Run tests in isolation
Running Tests
- Always use
uv run pytestto run tests - Never use
pip installor manual virtual environments - Example:
uv run pytest tests/ -v
Checking for Duplicates
- Run
uv run python scripts/check_duplicate_test_names.pybefore committing - Ensure no duplicate test names across different files
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.
- yesterday First seen · 52 lines · 0 tokens per session scan A 52537a907737
testing is a cursor rule published in the GitHub repository davidl71/project-management-automation (1 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 380 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
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.
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.