Oryntra: Agent for Claude Code

.claude/agents/test-runner.md

test-runner is an agent for Claude Code from andersonlemesc/Oryntra. It costs 89 tokens per session (744 once invoked), scanned A, original, Apache-2.0.

A testing agent for Oryntra’s Laravel and Python services, including Pest, pytest, and contract tests. Contract tests check that two connected services agree on request and response data.

In plain words
What is it for?
Use it to write, run, or fix feature, unit, and contract tests, or to increase test coverage after code changes.
Why use it?
It gives testing work a project-specific process, including test creation, execution, coverage, safe HTTP mocking, workspace isolation, duplicate webhook handling, and concurrent request checks.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions AGENTS.md.

This is andersonlemesc/Oryntra's own configuration. It tells Claude Code how to work on Oryntra itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Oryntra configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is docker compose exec laravel-app ./vendor/bin/pest --coverage --min=60.

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/andersonlemesc/Oryntra/main/.claude/agents/test-runner.md
Clone the repo
git clone --depth 1 https://github.com/andersonlemesc/Oryntra

Made for: Claude Code.

Wrote 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.

agentmods badge for test-runner

README.md
[![agentmods](https://agentmods.dev/badge/agents/andersonlemesc/oryntra/test-runner/github.svg)](https://agentmods.dev/agents/andersonlemesc/oryntra/test-runner)
Your own site
<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.

agentmods 80×15 button for test-runner

Your own site · 80×15
<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>
Per session 89 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 744 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 71acf8c4b46c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.claude/agents/test-runner.md · 55 lines

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)

  1. Toda mudança tem teste. Maioria são feature tests, não unit.
  2. Criar teste Laravel: php artisan make:test --pest --no-interaction {Nome}. NÃO incluir o diretório no nome (SomeFeatureTest, não Feature/SomeFeatureTest).
  3. Usar factories pro setup. Checar states customizados existentes antes de montar model na mão.
  4. Mock Chatwoot: Http::fake() (Laravel), httpx_mock (Python). Nunca chamada de rede real.
  5. workspace_id em toda query de negócio — testes de tenancy devem provar isolamento entre workspaces.
  6. Idempotência por chatwoot_message_id e lock por conversation_id — cobrir webhooks repetidos e respostas concorrentes quando relevante.
  7. Tokens sempre cast encrypted — verificar em testes de persistência.
  8. Cobertura mínima 60%: Pest --coverage --min=60, pytest --cov-fail-under=60.
  9. 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

  1. Ler o código sob teste e os testes/factories vizinhos pra casar estrutura e convenção.
  2. Escrever ou ajustar o teste. Feature test por padrão.
  3. Rodar o teste filtrado primeiro; depois a suíte relevante.
  4. Se quebrar: ler o erro exato, corrigir, repetir. Não mascarar com asserções fracas.
  5. Rodar vendor/bin/pint --dirty --format agent se editou PHP.
  6. Reportar: o que passou, o que falhou (com output), cobertura se pedida.

Read the full file on GitHub · 55 lines

Changes

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.

  1. 1mo ago First seen · 55 lines · 89 tokens per session scan A 71acf8c4b46c

Subscribe to this mod's changes

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.

Related

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.

athola/claude-night-market · 38 tokens

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.

echoVic/blade-code · 51 tokens

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.

felvieira/claude-skills-fv · 66 tokens

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.

mnzralee/claude-multi-agent-architecture · 41 tokens

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…

HirogaKatageri/hirokata · 77 tokens

implement-test-diversifier

Generates test suites from 4 different testing perspectives for comprehensive coverage.

eai-support/eai-gofer · 19 tokens