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/tecnomanu/pampa/auto-testgit clone --depth 1 https://github.com/tecnomanu/pampaWhat 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.00212 | $0.00212 |
| Opus 5 | $0.00106 | $0.00106 |
| Sonnet 5 | $0.00042 | $0.00042 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
auto-test 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 3d 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
Automated Testing
Run the test suite after each change and fix issues until all tests pass.
Testing Workflow
- Run Tests Frequently: Execute tests after implementing each logical component.
- Fix Issues Immediately: Address test failures as soon as they appear.
- Regression Testing: Ensure existing functionality remains intact.
- Test Coverage: Add new tests when implementing new features.
Common Test Commands
# Framework-specific test commands
npm test # Node.js/JavaScript
php artisan test # Laravel
ng test # Angular
mvn test # Java/Maven
pytest # Python
go test ./... # Go
Test-Driven Development
Consider adopting TDD principles:
- Write a failing test first
- Implement the minimal code to pass the test
- Refactor while keeping tests passing
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.
- 3d ago First seen · 37 lines · 212 tokens per session scan A 804149d8455a
auto-test is a cursor rule published in the GitHub repository tecnomanu/pampa (29 stars, last pushed 11mo ago), licensed ISC. It adds 212 tokens to every session, about $0.0011 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
cursor-behavior-constraints
Constraints on how Cursor should behave when designing and implementing UX, UI, IA, and accessibility patterns.
design-core
Balanced always-on core of UX, UI, IA, and accessibility principles for every interaction.
ia-navigation-and-structure
Information architecture patterns for navigation, structure, and labeling.
group_what_shares_common_meaning
Methods should group only lines of code that share a common intention. Different responsibilities must be extracted into separate methods or services.
comment_intelligently
Comments should provide context or clarifications that the code alone cannot convey. They are not a substitute for clear code, but a complement to explain why something is done or what external constraints apply.
limit_line_length_for_readability
Keep lines of code short enough to be easily readable and understandable at a glance. Long lines reduce readability, increase cognitive load, and complicate code reviews.