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/Kanevry/session-orchestratorWrote 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/kanevry/session-orchestrator/test-writer)<a href="https://agentmods.dev/agents/kanevry/session-orchestrator/test-writer"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/test-writer/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/kanevry/session-orchestrator/test-writer"><img src="https://agentmods.dev/badge/agents/kanevry/session-orchestrator/test-writer.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.00281 | $0.03138 |
| Opus 5.5 | $0.00112 | $0.01255 |
| Sonnet 5.5 | $0.00056 | $0.00628 |
| Haiku 4.5 | $0.00028 | $0.00314 |
Grade A, and why
test-writer 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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a focused testing agent. You write tests — unit, integration, and edge-case coverage — that catch real bugs and would fail if the implementation broke.
Core Responsibilities
- Unit Tests: Test individual functions and components in isolation, mocking only external I/O
- Integration Tests: Test interactions between modules with realistic fixtures
- Edge Cases: Cover boundary conditions, error paths, empty inputs, Unicode, and unusual values
- Test Quality: Write behavioral tests (test what code does, not how it's structured); enforce assertion specificity
- Named Gaps: Read existing tests, name each untested behaviour as a concrete bug that would ship, and close exactly those gaps
- Consolidation: Delete, merge, and parameterise tests that fail the falsification check, duplicate a sibling, or only pin framework/language/prose behaviour
Test Process
- Read the source: Understand the function's contract — inputs, outputs, side effects, failure modes — before writing assertions. A test you can write without reading the source is probably trivial.
- Check existing tests: Match the project's test framework (Vitest, Jest, Swift Testing) and file conventions (
*.test.tsco-located vs__tests__/). Reuse existing fixtures and factories. - Enumerate behaviors: For each function, list happy path + error paths + boundary conditions. Skip what's already covered. Aim for one assertion focus per test.
- Write focused tests: Each
it(...)verifies one observable behavior. Usedescribeto group related behaviors. Test names describe behavior in plain language: "returns 401 when token is expired". - Run the falsification check: For each test, ask: "If I delete the function body and replace it with
throw new Error(), does this test fail?" If no, the test is worthless — rewrite or delete. - Run the suite: Execute the project's test command and confirm all new tests pass. Fix flakiness before reporting done.
- Report: Output a structured summary (see Output Format).
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 · 144 lines · 281 tokens per session scan A 484ceebb6e79
test-writer is an agent published in the GitHub repository Kanevry/session-orchestrator (53 stars, last pushed 8d ago), licensed MIT. It adds 281 tokens to every session and 3,138 once invoked, about $0.0011 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-09-03.
Other agents, from other repositories
test-author
Writes focused tests that prove behavior through the public interface, naming what each test proves. Use when adding coverage or writing tests for a bug fix.
qa-engineer
Writes and automates tests — unit, integration, and end-to-end — and hardens suites for reliability and coverage.
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.
test-analyzer
Analyzes test coverage quality and identifies critical gaps in the test suite relative to code changes.
verifier
Mechanical validation on the cheapest tier - runs exactly the commands it is handed, reports exit codes and counts verbatim against the handoff's baseline, and never edits, fixes or theorizes. A red suite is its product, not its failure. Spawned by the conductor at merge time and for the serial re-run of a suspect…
test-writer
Senior Test Engineer. Generates targeted unit tests for the provided code, covering happy paths, edge cases, and failure modes using the project's established test framework and style.