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.
npx agentmods add agents/kanevry/session-orchestrator/test-writergit 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.svg" alt="Measured on agentmods" 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 | $0.00281 | $0.03138 |
| Opus 5 | $0.00140 | $0.01569 |
| Sonnet 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 yesterday.
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.
- yesterday First seen · 144 lines · 281 tokens per session scan A 484ceebb6e79
test-writer is an agent published in the GitHub repository Kanevry/session-orchestrator (49 stars, last pushed yesterday), licensed MIT. It adds 281 tokens to every session and 3,138 once invoked, about $0.0014 per session on Opus 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
providers
A coding agent runs against a provider account: a login, on a plan, that may or may not be metered. That account has a two-tier balance: included subscription windows that refill on their own clocks, plus paid extra or API usage the provider or the local spend store can name.
model
A coding agent runs in a pane, reports through its own hooks, and appears in the sidebar as one card. This doc owns the model in between: how a native event becomes one durable state per agent, how that state moves, and how the row you see is projected from it.
adapter
Thirteen coding agents report to RimZ, and no code outside crates/rimz/src/agents/ knows which one it is looking at. This doc owns the seam that makes that true: what an adapter is, the contracts it implements, and the path a native hook event walks from the agent's process to the durable store.
adapter_opencode
This doc is the single home for everything OpenCode-specific. OpenCode's integration surface is an in-process TypeScript plugin, so the adapter ships plugin.ts, embedded at compile time and installed as /.config/opencode/plugin/rimz.ts. The plugin subscribes to OpenCode hooks and bus events, flattens them into a…
adapter_pi
This doc is the single home for everything Pi-specific. Pi's integration surface is in-process TypeScript extensions, so the adapter ships one — extension.ts, embedded at compile time — that forwards each event below to rimz hooks feed --source pi as a fire-and-forget child. The child direction inverts: Claude and…
adapter_copilot
GitHub Copilot CLI reports through native camelCase command hooks installed as one RimZ-owned user file at $COPILOTHOME/hooks/rimz.json, falling back to /.copilot/hooks/rimz.json. Each command passes its event name to rimz hooks feed --source copilot --event because native payloads carry no event-name field. Hook…