Borrowing it
Nothing to install: this file belongs to reasvyn/docsgrep. 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/reasvyn/docsgrep/main/.agents/skills/test-writing/SKILL.mdgit clone --depth 1 https://github.com/reasvyn/docsgrepWrote 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/skills/reasvyn/docsgrep/test-writing)<a href="https://agentmods.dev/skills/reasvyn/docsgrep/test-writing"><img src="https://agentmods.dev/badge/skills/reasvyn/docsgrep/test-writing/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/skills/reasvyn/docsgrep/test-writing"><img src="https://agentmods.dev/badge/skills/reasvyn/docsgrep/test-writing.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.00016 | $0.00714 |
| Opus 5.5 | $0.00006 | $0.00286 |
| Sonnet 5.5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00002 | $0.00071 |
Grade A, and why
test-writing 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 2mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before writing tests
- Read
AGENTS.mdfor test commands and conventions. - Find an existing test file for a similar handler and copy its structure.
Run tests
bun run test # all tests
bun run vitest run tests/path/to.test.ts # single file
Unit test pattern
Place in tests/unit/. Mock all external IO at module level:
import { describe, it, expect, vi, beforeEach } from "vitest";
import { handleMyTool } from "../../../src/tools/my-tool.js";
vi.mock("node:fs/promises");
vi.mock("glob");
beforeEach(() => vi.resetAllMocks());
describe("handleMyTool", () => {
it("returns results", async () => {
vi.mocked(fs.stat).mockResolvedValue({ isDirectory: () => true } as any);
vi.mocked(glob).mockResolvedValue(["docs/readme.md"] as any);
const result = await handleMyTool({ dirPath: "/test" });
const data = JSON.parse(result.content[0].text);
expect(data).toHaveProperty("files");
expect(result.isError).toBeUndefined();
});
it("returns error for invalid path", async () => {
const result = await handleMyTool({ dirPath: "" });
expect(result.isError).toBe(true);
});
});
Key rules
- Mock at module level:
vi.mock('node:fs/promises'),vi.mock('glob'),vi.mock('simple-git'), etc. - Reset between tests:
beforeEach(() => vi.resetAllMocks()). - Parse responses: always
JSON.parse(result.content[0].text)before asserting on data. - Mock shapes: match real return types (e.g.,
fs.statneeds{ isDirectory: () => true }). - Conditional mocks: use
mockImplementationto return different values per input.
Integration test pattern
Place in tests/integration/. Spawns the real MCP server over stdio:
import { Client } from "@modelcontextprotocol/sdk";
import { StdioClientTransport } from "@modelcontextprotocol/sdk";
import path from "node:path";
import { fileURLToPath } from "node:url";
const __dirname = path.dirname(fileURLToPath(import.meta.url));
const serverPath = path.join(__dirname, "..", "..", "src", "index.ts");
let transport: StdioClientTransport;
let client: Client;
beforeAll(async () => {
transport = new StdioClientTransport({ command: "npx", args: ["tsx", serverPath] });
client = new Client({ name: "test-client", version: "1.0.0" }, { capabilities: {} });
await client.connect(transport);
}, 30000);
afterAll(async () => { await client.close(); });
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.
- 2mo ago First seen · 88 lines · 16 tokens per session scan A 236040fa1e71
test-writing is a skill published in the GitHub repository reasvyn/docsgrep (0 stars, last pushed 3mo ago), licensed MIT. It adds 16 tokens to every session and 714 once invoked, about $0.0001 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-31.
Other skills, from other repositories
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
principle-test-behavior-not-implementation
Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.
dart-test
DART Test: unit tests, integration tests, CI validation, and debugging.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.