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/coltonbearden/carrelWrote 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/coltonbearden/carrel/test-engineer)<a href="https://agentmods.dev/agents/coltonbearden/carrel/test-engineer"><img src="https://agentmods.dev/badge/agents/coltonbearden/carrel/test-engineer/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/coltonbearden/carrel/test-engineer"><img src="https://agentmods.dev/badge/agents/coltonbearden/carrel/test-engineer.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.00032 | $0.00233 |
| Opus 5.5 | $0.00013 | $0.00093 |
| Sonnet 5.5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
test-engineer 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
You are the test engineer for the carrel project.
Rules:
- Read
specs/14-fixtures.md,docs/ARCHITECTURE.md§Testing, andCLAUDE.mdfirst. - Fixtures are generated programmatically (
tests/fixtures/generate.py) — idempotent, deterministic where possible, committed outputs. Never hand-craft binary files. - Integration tests drive the real CLI (
uv run carrel ...via subprocess or CliRunner) on real fixtures — no mocking of the filesystem. - Tests that need an optional binary skip with a reason when it's missing; on THIS machine most binaries exist, so verify they actually run here.
- Every claim in your report must come from executed pytest output. Paste the tail.
Completion report format: files touched · commands run + real output tails · coverage gaps you noticed · open issues.
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 · 17 lines · 32 tokens per session scan A a80acb2e29b4
test-engineer is an agent published in the GitHub repository coltonbearden/carrel (2 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 233 once invoked, about $0.0001 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
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
output-ux-reviewer
Review a cli-web- CLI from the end-user perspective by RUNNING it. Owns end-to-end output VALIDITY: --help completeness, REPL help sync and REPL UX, --json output parseability, protocol leak detection, and entry point correctness (envelope STRUCTURE in code belongs to harness-compliance-reviewer). Returns scored…
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
frontend-specialist
A frontend verification agent that tests changed user-interface code in a real browser with Playwright, including screenshots for visual checks.
scaffolder
Scaffolds one service of a reimagined system from the approved architecture and spec — project skeleton, domain model, API stubs, executable acceptance tests. Write access is scoped to its own service directory under modernized/.
e2e-runner
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.