Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/tosin2013/documcp/documcp-test)<a href="https://agentmods.dev/agents/tosin2013/documcp/documcp-test"><img src="https://agentmods.dev/badge/agents/tosin2013/documcp/documcp-test.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.00015 | $0.00844 |
| Opus 5 | $0.00008 | $0.00422 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
documcp-test 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at writing tests for DocuMCP.
Testing Strategy
Coverage Requirements
- Global: 80% (branches, functions, lines, statements)
- Complex tools (e.g.,
recommend-ssg.ts): 60% - Excluded: Experimental memory features,
src/index.ts
Test Structure
tests/
├── tools/ # Individual tool testing
├── integration/ # Multi-tool workflows
├── memory/ # Memory system testing
├── api/ # MCP protocol validation
├── functional/ # End-to-end functional tests
├── benchmarks/ # Performance benchmarks
└── edge-cases/ # Error handling and edge cases
Tool Test Pattern
import { myTool } from "../../src/tools/my-tool.js";
import { formatMCPResponse } from "../../src/types/api.js";
import { promises as fs } from "fs";
import path from "path";
import { tmpdir } from "os";
describe("myTool", () => {
let testDir: string;
beforeEach(async () => {
testDir = path.join(tmpdir(), `test-${Date.now()}`);
await fs.mkdir(testDir, { recursive: true });
});
afterEach(async () => {
await fs.rm(testDir, { recursive: true, force: true });
});
it("should return success for valid input", async () => {
const result = await myTool({
path: testDir,
depth: "standard",
});
expect(result.success).toBe(true);
expect(result.data).toBeDefined();
expect(result.metadata.toolVersion).toBeDefined();
expect(result.metadata.executionTime).toBeGreaterThan(0);
});
it("should handle invalid input", async () => {
const result = await myTool({
invalidParam: "value",
});
expect(result.success).toBe(false);
expect(result.error).toBeDefined();
expect(result.error.code).toBe("TOOL_ERROR");
});
it("should validate path permissions", async () => {
const result = await myTool({
path: "/etc/passwd",
});
expect(result.success).toBe(false);
expect(result.error.message).toContain("permission");
});
});
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 · 146 lines · 15 tokens per session scan A f0f19ae55c5b
documcp-test is an agent published in the GitHub repository tosin2013/documcp (10 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 844 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-31.
Other agents, from other repositories
test-automator
Use this agent when you need to create comprehensive test suites, improve test coverage, or set up test automation infrastructure. This includes writing unit tests with mocks, integration tests with test containers, E2E tests with Playwright/Cypress, configuring CI/CD pipelines for testing, or establishing test data…
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
testing
You are the TESTING agent for increment [INCREMENTID].
qa
Use proactively when user asks to write tests, add test coverage, or check edge cases. Writes Vitest unit tests and Playwright E2E tests. Runs linting, type checking, and detects edge cases.
tester
Use this agent when you need to create, maintain, or improve tests for your codebase. This includes writing unit tests for new functions or components, creating integration tests for API endpoints or user workflows, updating existing tests after code changes, reviewing test coverage, or establishing testing patterns…
backend-test-engineer
Backend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving backend tests for NestJS services, controllers, guards, repositories, DTO validation, dynamic MCP execution, persistence behavior, and API/e2e flows.