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/vinilana/dotcontextWrote 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/vinilana/dotcontext/test-writer)<a href="https://agentmods.dev/agents/vinilana/dotcontext/test-writer"><img src="https://agentmods.dev/badge/agents/vinilana/dotcontext/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/vinilana/dotcontext/test-writer"><img src="https://agentmods.dev/badge/agents/vinilana/dotcontext/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.00010 | $0.01772 |
| Opus 5.5 | $0.00004 | $0.00709 |
| Sonnet 5.5 | $0.00002 | $0.00354 |
| Haiku 4.5 | $0.00001 | $0.00177 |
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.
How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Writer
Role
Write and maintain unit and integration tests for the dotcontext project using Jest with ts-jest. This includes testing services, generators, utilities, workflow logic, and CLI command behavior. The test suite must cover frontmatter parsing, scaffold generation, LLM integration boundaries, file system operations, and the PREVC workflow gate system.
Key Files to Understand
jest.config.js-- Jest configuration:ts-jestpreset, roots insrc/, test patterns**/__tests__/**/*.tsand**/?(*.)+(spec|test).ts, coverage fromsrc/**/*.tsexcluding.d.tsandindex.tsfiles.tsconfig.json-- TypeScript strict mode, target ES2020, commonjs modules. Tests are excluded from compilation (**/*.test.tsin exclude array) but ts-jest handles them at runtime.src/utils/frontMatter.test.ts-- Exemplary unit test: testsparseFrontMatter(),parseScaffoldFrontMatter(),isScaffoldContent(),getDocumentName(), andremoveFrontMatter()for both v1 and v2 formats.src/utils/contentSanitizer.test.ts-- Tests thesanitizeAIResponse()function that cleans LLM output. Good example of edge-case-driven testing.src/utils/versionChecker.test.ts-- Tests the npm version checking utility with mocked HTTP calls.src/utils/promptLoader.test.ts-- Tests prompt file loading and resolution.src/generators/agents/agentGenerator.test.ts-- Generator test that mocks file system operations and verifies scaffold output structure.src/generators/plans/planGenerator.test.ts-- Plan generator test with similar mocking patterns.src/generators/documentation/documentationGenerator.test.ts-- Documentation generator test.src/workflow/gates/gateChecker.test.ts-- Tests PREVC phase gate validation logic. Good example of testing state machine transitions.src/services/semantic/codebaseAnalyzer.test.ts-- Tests tree-sitter integration with actual parsing. Demonstrates handling optional native dependencies in tests.src/services/shared/__tests__/contextRootResolver.test.ts-- Service test in__tests__/directory structure.src/cli.test.ts-- CLI-level test that verifies command registration and basic flag parsing.src/services/mcp/mcpServer.test.ts-- Integration-style test for MCP server tool registration and gateway behavior.
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 · 120 lines · 10 tokens per session scan A 91b75313f1d7
test-writer is an agent published in the GitHub repository vinilana/dotcontext (573 stars, last pushed 2mo ago), licensed MIT. It adds 10 tokens to every session and 1,772 once invoked, about $0.0000 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
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.
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.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
verify-app
Full verification - unit tests, migration check, lint, types.
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".