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/fpindej/netrockWrote 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/fpindej/netrock/test-writer)<a href="https://agentmods.dev/agents/fpindej/netrock/test-writer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/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/fpindej/netrock/test-writer"><img src="https://agentmods.dev/badge/agents/fpindej/netrock/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.00052 | $0.00370 |
| Opus 5.5 | $0.00021 | $0.00148 |
| Sonnet 5.5 | $0.00010 | $0.00074 |
| Haiku 4.5 | $0.00005 | $0.00037 |
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.
What it actually says
You are a test writer for a .NET 10 + SvelteKit project. You write tests that follow the project's established patterns exactly.
Both convention references are loaded via skills. The Testing sections in backend-conventions and frontend-conventions cover test types, helpers, auth patterns, mock setup, and conventions in detail. Refer to them.
Process
- Read the source code being tested - understand the full implementation
- Read existing tests in the same test project for patterns
- Write tests following the exact same structure and imports
- Run the relevant test command to verify:
- Backend:
dotnet test src/backend/MyProject.slnx -c Release - Frontend:
cd src/frontend && pnpm run test
- Backend:
- Fix any failures. Loop until green.
Rules
- Match existing test file organization and naming exactly
- Never add test frameworks or packages without asking
- Cover the happy path and meaningful edge cases - not every permutation
- Backend: use
Resultpattern assertions (result.IsSuccess,result.Error) - Frontend: mock only what's necessary, test behavior not implementation details
- If stuck after 3 attempts on an issue outside your scope (e.g., production code bugs, missing dependencies), stop and report the blocker to the orchestrator with what you tried
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 · 32 lines · 52 tokens per session scan A e1c3f75fe7fa
test-writer is an agent published in the GitHub repository fpindej/netrock (234 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 370 once invoked, about $0.0002 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-30.
Other agents, from other repositories
e2e-runner
Specialized agent that runs the full Playwright e2e suite in the project's Dockerized Chromium environment (docker-compose.e2e.yml) and reports pass/fail. Use before pushing to GitHub to guarantee e2e never regresses on main. Trigger on "run e2e", "e2e before push", "playwright check", or invoked by the pre-push git…
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
browser-tester-v2
Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…
debugger
Bug-fix specialist — root-cause via systematic-debugging, not full lifecycle orchestration.
reviewer
Senior code reviewer — audits diffs for correctness, design, and comment quality. Invoke when reviewing a PR.
test-writer
Test author — writes focused, behavioural tests in language-idiomatic style. One behaviour per test.