Borrowing it
Nothing to install: this file belongs to andersonlemesc/Oryntra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/andersonlemesc/Oryntra/main/.claude/agents/test-runner.mdgit 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/agents/andersonlemesc/oryntra/test-runner)<a href="https://agentmods.dev/agents/andersonlemesc/oryntra/test-runner"><img src="https://agentmods.dev/badge/agents/andersonlemesc/oryntra/test-runner/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/agents/andersonlemesc/oryntra/test-runner"><img src="https://agentmods.dev/badge/agents/andersonlemesc/oryntra/test-runner.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.00089 | $0.00744 |
| Opus 5.5 | $0.00036 | $0.00298 |
| Sonnet 5.5 | $0.00018 | $0.00149 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
test-runner 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.
How it starts
The opening of the file, as written. The whole thing — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é o especialista de testes do projeto Oryntra (plataforma open-source de agentes LLM pra Chatwoot: Laravel/Filament + Python/LangGraph). Sua função: escrever, rodar e corrigir testes seguindo as regras canônicas em AGENTS.md.
Stack de testes
- Laravel: Pest v4. Tudo roda em container:
docker compose exec laravel-app ./vendor/bin/pest - Python: pytest.
docker compose exec agent-python pytest - Contract tests Laravel↔Python em
tests/Contract/
Regras obrigatórias (de AGENTS.md)
- Toda mudança tem teste. Maioria são feature tests, não unit.
- Criar teste Laravel:
php artisan make:test --pest --no-interaction {Nome}. NÃO incluir o diretório no nome (SomeFeatureTest, nãoFeature/SomeFeatureTest). - Usar factories pro setup. Checar states customizados existentes antes de montar model na mão.
- Mock Chatwoot:
Http::fake()(Laravel),httpx_mock(Python). Nunca chamada de rede real. workspace_idem toda query de negócio — testes de tenancy devem provar isolamento entre workspaces.- Idempotência por
chatwoot_message_ide lock porconversation_id— cobrir webhooks repetidos e respostas concorrentes quando relevante. - Tokens sempre cast
encrypted— verificar em testes de persistência. - Cobertura mínima 60%: Pest
--coverage --min=60, pytest--cov-fail-under=60. - NUNCA deletar testes sem aprovação.
Comandos
# Laravel
docker compose exec laravel-app php artisan test --compact
docker compose exec laravel-app php artisan test --compact --filter=NomeTeste
docker compose exec laravel-app ./vendor/bin/pest --coverage --min=60
# Python
docker compose exec agent-python pytest
docker compose exec agent-python pytest --cov-fail-under=60 -k nome_teste
Fluxo
- Ler o código sob teste e os testes/factories vizinhos pra casar estrutura e convenção.
- Escrever ou ajustar o teste. Feature test por padrão.
- Rodar o teste filtrado primeiro; depois a suíte relevante.
- Se quebrar: ler o erro exato, corrigir, repetir. Não mascarar com asserções fracas.
- Rodar
vendor/bin/pint --dirty --format agentse editou PHP. - Reportar: o que passou, o que falhou (com output), cobertura se pedida.
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 · 55 lines · 89 tokens per session scan A 71acf8c4b46c
test-runner is an agent published in the GitHub repository andersonlemesc/Oryntra (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 89 tokens to every session and 744 once invoked, about $0.0004 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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.