Borrowing it
Nothing to install: this file belongs to ZapSign/api-mcp. 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/ZapSign/api-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/ZapSign/api-mcpWrote 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/instructions/zapsign/api-mcp/agents-md)<a href="https://agentmods.dev/instructions/zapsign/api-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zapsign/api-mcp/agents-md/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/instructions/zapsign/api-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/zapsign/api-mcp/agents-md.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.01779 | $0.01779 |
| Opus 5.5 | $0.00712 | $0.00712 |
| Sonnet 5.5 | $0.00356 | $0.00356 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
api-mcp AGENTS.md 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ZapSign MCP Server — Agent Instructions
Project Overview
Remote MCP server connecting Claude AI to ZapSign's electronic signature API via Cloudflare Workers. Stack: TypeScript strict, Cloudflare Workers, @modelcontextprotocol/sdk ^1.27.0, agents 0.6.0, OAuth 2.1.
Dev Commands
npm run dev # wrangler dev (local server)
npm run typecheck # tsc --noEmit
npm run lint # eslint src/
npm run test # vitest run
npm run test:watch # vitest watch
npm run deploy # wrangler deploy
Architecture
src/index.ts— Worker entry point (OAuthProvider wiring)src/server.ts— McpServer factory (new instance per request)src/auth/— OAuth handler, API token validation, token exchange passthroughsrc/api/— ZapSign HTTP client wrapper, endpoint constantssrc/tools/— full MCP tool union (documents, signers, templates, webhooks, partner) + STDIO entry insrc/stdio/src/errors/— Error class hierarchy (base, api, auth, validation)src/types/— Cloudflare Env bindings, ZapSign API typessrc/utils/— Logger, MCP response formatters, scope enforcement
Coding Standards
These are non-negotiable constraints. Every agent MUST follow them.
Language Rules
- All identifiers in English: variable names, function names, class names, type names, enum values
- All comments in English: only write comments that explain WHY, never WHAT
- No narration comments: never write
// Create the clientbeforeconst client = new Client() - JSDoc only on exported functions: with
@param,@returns,@throws
Structural Rules
- Early return pattern: always. Guard clauses at the top of every function.
- No
elseafterreturn: ever. Use early return instead. - No
elseblocks: restructure with early returns or ternaries. - No
switchstatements: use object maps (Record<string, handler>) or strategy pattern. - Maximum 2 levels of nesting: if inside an
ifinside afor, that's 2. Extract to a function. - Cyclomatic complexity < 10: per function. Prefer extracting helpers.
- Cognitive complexity < 10: per function.
- Maximum function length: 40 lines (excluding type signatures and JSDoc).
- Single responsibility: each function does ONE thing.
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 · 171 lines · 1,779 tokens per session scan A 05a7091741e4
api-mcp AGENTS.md is an instructions file published in the GitHub repository ZapSign/api-mcp (1 stars, last pushed 7d ago), licensed MIT. It adds 1,779 tokens to every session, about $0.0071 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).