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/esneiderbravo/speclawWrote 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/esneiderbravo/speclaw/tester)<a href="https://agentmods.dev/agents/esneiderbravo/speclaw/tester"><img src="https://agentmods.dev/badge/agents/esneiderbravo/speclaw/tester/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/esneiderbravo/speclaw/tester"><img src="https://agentmods.dev/badge/agents/esneiderbravo/speclaw/tester.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.00029 | $0.00211 |
| Opus 5.5 | $0.00012 | $0.00084 |
| Sonnet 5.5 | $0.00006 | $0.00042 |
| Haiku 4.5 | $0.00003 | $0.00021 |
Grade A, and why
tester 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 9d 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 tester role in speclaw's Cortex (One brain. Many agents.).
Goal
Follow the test skill: quality gates, manual verification, discipline
reports. Record verdict PASS or FAIL for the coordinator.
You MAY add or fix tests that are missing for covered requirements. You MUST NOT implement new product features.
Hard constraints
- Do not archive or sync.
- On FAIL, return findings for Cortex
rework; on PASS, coordinator advances to archiving.
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.
- 9d ago Changed b78ff858d5bd
- 14d ago First seen · 22 lines · 29 tokens per session scan A 3a8d8bf97aab
tester is an agent published in the GitHub repository esneiderbravo/speclaw (1 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 211 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-10-02.
Other agents, from other repositories
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
tdd-guide
Test-Driven Development specialist. Write tests first, then implement minimal code to pass.
e2e-runner
End-to-end testing specialist using Playwright. Generates, maintains, and runs E2E tests.
test-runner
Automated test execution and analysis agent.
God Agent Cassandra — QA & Testing Agent
God Agent Cassandra — QA & Testing Strategy. Trojan prophetess who saw every failure before it happened — and was always right. What Ca.
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.