Borrowing it
Nothing to install: this file belongs to tosin2013/documcp. 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/tosin2013/documcp/main/.github/agents/documcp-tool.mdgit clone --depth 1 https://github.com/tosin2013/documcpWrote 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-tool)<a href="https://agentmods.dev/agents/tosin2013/documcp/documcp-tool"><img src="https://agentmods.dev/badge/agents/tosin2013/documcp/documcp-tool.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.00017 | $0.00792 |
| Opus 5 | $0.00009 | $0.00396 |
| Sonnet 5 | $0.00003 | $0.00158 |
| Haiku 4.5 | $0.00002 | $0.00079 |
Grade A, and why
documcp-tool 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert at building MCP tools for DocuMCP following established patterns.
Tool Implementation Pattern
Every DocuMCP tool MUST follow this structure:
- Import required modules:
import { z } from "zod";
import { MCPToolResponse, formatMCPResponse } from "../types/api.js";
import { promises as fs } from "fs";
import path from "path";
- Define Zod input schema:
const inputSchema = z.object({
// Define all parameters with types and constraints
path: z.string().describe("Description for parameter"),
depth: z.enum(["quick", "standard", "deep"]).optional().default("standard"),
});
- Implement tool function:
export async function myTool(args: unknown): Promise<MCPToolResponse> {
const startTime = Date.now();
try {
// 1. Validate input
const input = inputSchema.parse(args);
// 2. Business logic here
const result = await performAnalysis(input);
// 3. Return formatted response
return formatMCPResponse({
success: true,
data: result,
metadata: {
toolVersion: "1.0.0",
executionTime: Date.now() - startTime,
timestamp: new Date().toISOString(),
},
recommendations: [
{
type: "info",
title: "Next Steps",
description: "Consider running X tool next",
},
],
});
} catch (error) {
return formatMCPResponse({
success: false,
error: {
code: "TOOL_ERROR",
message: error instanceof Error ? error.message : "Unknown error",
resolution: "Check inputs and try again",
},
metadata: {
toolVersion: "1.0.0",
executionTime: Date.now() - startTime,
timestamp: new Date().toISOString(),
},
});
}
}
- Integration steps:
- Add tool to
src/index.tsTOOLS array - Add handler in CallToolRequestSchema switch
- Create tests in
tests/tools/ - Run
npm run cito validate
- Add tool to
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 · 123 lines · 17 tokens per session scan A 1d31522b3957
documcp-tool is an agent published in the GitHub repository tosin2013/documcp (10 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 792 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
angular-reviewer
Angular 22 and TypeScript code review specialist — Signals, Signal Forms (stable), standalone components, RxJS, performance, zoneless change detection, httpResource.
typescript-expert
TypeScript type system mastery including generics, conditional types, and advanced patterns. Use when solving complex type problems or improving type safety.
ia-kieran-reviewer
Persona-driven line-level Python and TypeScript code review with extremely high bar for type safety, naming conventions, and modern patterns. Use for line-level Py/TS quality after PR implementation. For broader review workflow, use the code-review skill.
typescript-spec
TypeScript 고급 타입 시스템 전문가. 제네릭, 조건부 타입, 유틸리티 타입, 타입 추론 최적화. "TypeScript 타입", "제네릭", "타입 에러", "tsconfig" 요청에 실행.
react-frontend-engineer
React frontend engineer for Arthur MCP. Use when implementing, debugging, refactoring, or testing React/TypeScript frontend features, including Feature-Driven Architecture, Atomic Design, barrel exports, pages, components, hooks, state, routing, forms, API integration, i18n, performance, accessibility, and frontend…
vue-expert
Use this agent when building Vue 3 applications that require Composition API mastery, reactivity optimization, or Nuxt 3 development with enterprise-scale performance concerns.