Borrowing it
Nothing to install: this file belongs to klboke/kkRepo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/klboke/kkRepo/main/.github/agents/test-writer.mdgit clone --depth 1 https://github.com/klboke/kkRepoWrote 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/klboke/kkrepo/test-writer)<a href="https://agentmods.dev/agents/klboke/kkrepo/test-writer"><img src="https://agentmods.dev/badge/agents/klboke/kkrepo/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.00012 | $0.00143 |
| Opus 5 | $0.00006 | $0.00072 |
| Sonnet 5 | $0.00002 | $0.00029 |
| Haiku 4.5 | $0.00001 | $0.00014 |
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 6d 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 add focused tests for kkRepo changes.
Rules:
- Use the existing test style and helpers.
- Prefer narrow unit tests for small behavior changes.
- Add compatibility tests under
compat-testfor protocol behavior changes. - For
servertests, run Maven with-amand-Dsurefire.failIfNoSpecifiedTests=falsewhen selecting specific tests. - Cover concurrency, rollback, duplicate writes, cache invalidation, auth, and permission behavior when touched.
Keep implementation changes minimal unless needed to make the testable behavior correct.
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.
- 6d ago First seen · 18 lines · 12 tokens per session scan A 8ab54746871c
test-writer is an agent published in the GitHub repository klboke/kkRepo (260 stars, last pushed 6d ago), licensed Apache-2.0. It adds 12 tokens to every session and 143 once invoked, about $0.0001 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-30.
Other agents, from other repositories
imperial-censor
御史台·代天巡狩：全系统独立审查权力机构，直达董事长。三方制衡的测试+审查方——独立写测试（先 RED）+ 7 维 Code Review。事实高于人设，无罪不弹，规范之外不开刀。.
dependency-manager
Dependency management, version upgrades, and compatibility specialist.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
tester
테스트 작성 전담 에이전트. 단위/통합/E2E 테스트를 설계하고 구현하며, 커버리지 목표 달성을 책임진다.
pydantic-ai-validator
Testing and validation specialist for Pydantic AI agents. USE AUTOMATICALLY after agent implementation to create comprehensive tests, validate functionality, and ensure readiness. Uses TestModel and FunctionModel for thorough validation.
test-expert-csk
Test expert. Use proactively after new handler/endpoint/agent behavior is added: writes and runs unit/integration tests and guarantees the DoD's "tests are green".