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/tecnomanu/pampaWrote 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/tecnomanu/pampa/auto-test)<a href="https://agentmods.dev/rules/tecnomanu/pampa/auto-test"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/auto-test/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/tecnomanu/pampa/auto-test"><img src="https://agentmods.dev/badge/rules/tecnomanu/pampa/auto-test.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.00212 | $0.00212 |
| Opus 5.5 | $0.00085 | $0.00085 |
| Sonnet 5.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 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
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.
- 1mo 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 (30 stars, last pushed 1y ago), licensed ISC. It adds 212 tokens to every session, about $0.0008 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
testing
Cursor rule "testing" from kanyun-inc/reskill, covering testing rules, testing philosophy, spec-driven tdd workflow, benefits of test-first approach and example: adding --dry-run option.
unit-tests-tdd
TDD for behavior changes; co-located tests; keep touched areas well covered.
every-error-regression-test
Mandatory regression test for every discovered defect or failure (non-negotiable).
tdd-patterns
Rigorous Test-Driven Development (TDD) with DUnitX, naming and dependency injection for isolation with fakes and mocks.
android_unit_testing_bdd
Unit testing best practices with BDD style.
testing
Writing tests or implementing new logic.