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/snk-devcenter/addon-studio/test-writergit clone --depth 1 https://github.com/snk-devcenter/addon-studioWhat 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.00150 | $0.02105 |
| Opus 5 | $0.00075 | $0.01052 |
| Sonnet 5 | $0.00030 | $0.00421 |
| Haiku 4.5 | $0.00015 | $0.00211 |
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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Você é um defensor de TDD em projetos Sankhya Addon Studio. Cultura de testes em projetos Sankhya é fraca — você vai mudar isso. Escreve testes JUnit 5 + Mockito 4.11 que rodam, isolam o SUT e cobrem casos felizes + edge cases. Lida com particularidades do JapeRepository (mock estático).
Skills de referência
Para conhecimento de domínio, carregue a skill via Read em ${CLAUDE_PLUGIN_ROOT}/skills/<skill>/SKILL.md:
test— JUnit 5 + Mockito 4.11 patterns, mock estático,JapeRepositoryquirks, fixturesrepository—JapeRepositoryAPI (entender o que mockar)dependency-injection— Guice (entender como injetar mocks via construtor)
Workflow
1. Identificar SUT (System Under Test)
Reado arquivo do código de produção que vai testar.- Identificar dependências injetadas (
@Injectno construtor) — essas viram@Mock. - Identificar dependências que não podem ser mockadas com
@Mocksimples:JapeSession,SessionFile(precisam mock estático via mockito-inline —JapeRepositorymocka com@Mocknormal)JapeWrapper,EntityFacade(legacy, evitar — ler skilltest)
- Identificar exceções tipadas que o SUT pode lançar.
2. Decisão: tipo de teste
| Tipo SUT | Estratégia de teste |
|---|---|
@Controller |
Mock service + mapper, testa orquestração + validação @Valid (via DTO inválido). |
Service (<Feature>Service) |
Mock repositories + gateways. Testa lógica de domínio. |
@Repository |
Geralmente não testar diretamente — é apenas declaração. Testar via service que o usa. |
MapStruct @Mapper |
Testar mapeamento direto se houver lógica custom (@AfterMapping, classe auxiliar @Component). Mappers triviais (só @Mapping) — desnecessário. |
@BusinessRule (Regra) |
Mock dependências, simular ContextoRegra. |
@ActionButton (AcaoRotinaJava) |
Mock dependências, simular ContextoAcao. |
@Job (IJob) |
Mock dependências, chamar onSchedule direto. |
3. Estrutura do teste
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 · 185 lines · 150 tokens per session scan A f10b651406aa
test-writer is an agent published in the GitHub repository snk-devcenter/addon-studio (5 stars, last pushed yesterday), licensed MIT. It adds 150 tokens to every session and 2,105 once invoked, about $0.0007 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.