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/andersonlemesc/OryntraWrote 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/andersonlemesc/oryntra/testing)<a href="https://agentmods.dev/rules/andersonlemesc/oryntra/testing"><img src="https://agentmods.dev/badge/rules/andersonlemesc/oryntra/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/andersonlemesc/oryntra/testing"><img src="https://agentmods.dev/badge/rules/andersonlemesc/oryntra/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.00005 | $0.00236 |
| Opus 5.5 | $0.00002 | $0.00094 |
| Sonnet 5.5 | $0.00001 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00024 |
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 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
Testes Oryntra
Laravel (Pest)
- Toda feature/bug fix tem teste
php artisan make:test --pest --no-interaction NomeTest- Mock Chatwoot via
Http::fake() - Factories pra setup; checar states existentes antes de criar manual
- Coverage mínimo:
./vendor/bin/pest --coverage --min=60
Python (pytest)
pytest tests/com--cov=src --cov-fail-under=60- Mock HTTP via
httpx_mock - Async tests com
pytest-asyncio - Fixtures pra DB/Redis em
tests/conftest.py
Contract tests (Laravel ↔ Python)
tests/Contract/em Laravel +tests/contract/em Python- Validam payloads de request/response consistentes
- Rodam em
ci-contract.ymlcom stack mínima docker
Browser/E2E
- Adiar pra Fase 6+
- Avaliar Pest 4 browser plugin ou Dusk
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 · 29 lines · 5 tokens per session scan A c4e945f57b90
testing is a cursor rule published in the GitHub repository andersonlemesc/Oryntra (7 stars, last pushed today), licensed Apache-2.0. It adds 5 tokens to every session and 236 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
300-testing
Comprehensive testing guide covering unit, integration, E2E, test frameworks, patterns, and CI/CD integration.
hatch3r-testing
Coverage thresholds, mocking strategy, property-based testing, mutation-score targets, flaky test quarantine, and snapshot test discipline.
30-testing
Convenciones de testing, cobertura mínima, tipos de tests, mocks.
tester
Tester role - Unit, E2E, and visual regression testing.
go-test
Rules for writing and modifying test files (test.go) in go-crypto-wallet.
do-runner
Use the following runners.