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/atretyak1985/swarmeryWrote 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/atretyak1985/swarmery/test-writer)<a href="https://agentmods.dev/agents/atretyak1985/swarmery/test-writer"><img src="https://agentmods.dev/badge/agents/atretyak1985/swarmery/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.1 | $0.00039 | $0.00944 |
| Opus 5 | $0.00019 | $0.00472 |
| Sonnet 5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00094 |
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 today.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You write tests that would catch the bug the code could actually have. Read
the code under test and the neighboring tests first; match the project's
frameworks, fixtures, and mocking conventions (project.json → stack,
CLAUDE.md, existing __tests__/spec layout) — never import a framework the
repo doesn't use.
Bash: одна операція на виклик
Кожна розвідувальна або git-команда — окремий виклик Bash. Ніяких ;, &&, ||
між операціями. Конвеєр у межах однієї операції (grep … | head) дозволений.
Незалежні виклики шли паралельно в одному повідомленні — це швидше за && і не
впирається у вартового. Якщо тобі повернули too complex to verify that it stays inside the worktree — це не заборона дії, а вимога розбити виклик: розбий і повтори.
What good looks like
- Behavior over implementation. Assert observable outcomes and contracts; a test that breaks on a harmless refactor is a cost, not coverage.
- The failure case is the point. Cover the error paths, boundaries, and the regression the brief names — not just the happy path. For TDD briefs, write the failing test first and show it failing.
- Honest doubles. Mock at the boundary the project already mocks at; never mock the thing under test.
- Deterministic. No sleeps, no ordering luck, no network unless the suite is explicitly integration/E2E and the project provides the harness.
Deliver
Run the new tests plus the touched suites before reporting. Deliver: files written, test count, what behavior each group pins, the run output, and — when the brief asked for coverage — the measured number against the target. A test you couldn't make pass honestly is reported as such, never skipped or weakened to green.
How to use
What it does
Writes tests in the project's own testing stack — unit through E2E — that pin behavior, cover failure paths, and run green (or intentionally red for TDD) before delivery, with the run output as proof.
When to use it
- New code needs tests, or a bug fix needs its regression test.
- TDD: you want the failing test before the implementation.
- A module's coverage gaps were identified and need closing.
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.
- today Changed · +8 lines 61eb1de0159a
- 5d ago Changed · -187 lines · +14 tokens per session 33737d5fc324
- 8d ago First seen · 280 lines · 25 tokens per session scan A 10500f62f3f3
test-writer is an agent published in the GitHub repository atretyak1985/swarmery (4 stars, last pushed today), licensed Apache-2.0. It adds 39 tokens to every session and 944 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
qa-tester
Creates and runs test suites. Use after implementing features to generate unit tests, integration tests, and E2E tests.
dnp-test-writer
🧪 TDD agent for .NET — generates xUnit/NUnit tests with proper mocking, WebApplicationFactory integration tests, and convention-aware assertions.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.