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.
npx agentmods add instructions/nizoka/pdfnative-mcp/mcp-servergit clone --depth 1 https://github.com/Nizoka/pdfnative-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/nizoka/pdfnative-mcp/mcp-server)<a href="https://agentmods.dev/instructions/nizoka/pdfnative-mcp/mcp-server"><img src="https://agentmods.dev/badge/instructions/nizoka/pdfnative-mcp/mcp-server.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 | $0.00895 | $0.00895 |
| Opus 5 | $0.00447 | $0.00447 |
| Sonnet 5 | $0.00179 | $0.00179 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
pdfnative-mcp mcp-server.instructions.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 4d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Server Standards
Transport and lifecycle
- stdio transport by default; Streamable HTTP when
PDFNATIVE_MCP_PORTis set (loopback bind + Host/Origin guard; opt-in bearer token viaPDFNATIVE_MCP_HTTP_TOKEN, seesrc/auth.ts). - SDK:
@modelcontextprotocol/server^2.0.0 (MCP 2026-07-28, automatic 2025-era fallback). - Gracefully close the server on SIGINT/SIGTERM.
- Avoid writing to stdout except MCP protocol payloads (use stderr for logs).
Tool contract
- Each tool module exports:
TOOL_NAME,TOOL_INPUT_SCHEMA, optionalTOOL_OUTPUT_SCHEMAhandler(args: unknown)
- Keep JSON schema and Zod validation aligned; Zod schemas are
.strict()(unknown top-level or nested keys →VALIDATION_ERROR, matchingadditionalProperties: false). - Decode
pdfBase64/ DER inputs throughsrc/base64.ts(data: URI tolerated; PEM-vs-DER, double-encoding and empty-payload hints). - Return tool-level errors as
isErrorresponses with actionable messages — never throw across the MCP boundary. The one protocol-level exception: an unknown tool name ontools/callis a JSON-RPC-32602error with message[UNKNOWN_TOOL] Unknown tool: <name>. - Every tool registered in
src/server.tsmust ship_meta.apiVersion(currentTOOL_API_VERSION, seedocs/API_STABILITY.md) and one or two executable_meta.examples(they are validated againstinputSchemain tests; more examples belong inexamples/*.json). tools/liststructure is pinned bytests/_fixtures/tool-shape.json(tests/catalogue-parity.test.ts). Wording is free; any change to types, enums, defaults, constraints,required,additionalPropertiesor example count needsnode scripts/tool-shape.mjs --writeand a review underdocs/API_STABILITY.md§5.tests/catalogue-superset.test.tsadditionally rejects any removal / narrowing against the frozen 1.5.0 fixture (tests/_fixtures/tool-shape.v1.5.0.json).- No
$ref/$defsand no$schemakeyword in input schemas (host compatibility); the 13-kind block union is therefore repeated ininspect_layoutby design. - Update
SERVER_INSTRUCTIONS(decision tree + pitfalls) whenever you add a tool or change its behaviour.
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.
- 4d ago First seen · 36 lines · 895 tokens per session scan A 72032e24880a
pdfnative-mcp mcp-server.instructions.md is an instructions file published in the GitHub repository Nizoka/pdfnative-mcp (2 stars, last pushed 11d ago), licensed MIT. It adds 895 tokens to every session, about $0.0045 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 instructions, from other repositories
docs-to-pdf CLAUDE.md
Claude Code instructions for jean-humann/docs-to-pdf, covering claude development guide for docs-to-pdf, project overview, development environment setup, using mise (recommended) and install mise (if not already installed).
Portwood CLAUDE.md
Instructions for Portwood-Global-Solutions/Portwood, covering claude.md — portwood, skills, how this project runs (from 2026-08-10), release cadence and triage.
prfaq CLAUDE.md
Instructions for punt-labs/prfaq, covering how i write code, mandatory reading, no "pre-existing" excuse, standards and development workflow.
nutrient-dws-client-typescript AGENTS.md
Instructions for PSPDFKit-labs/nutrient-dws-client-typescript, covering agents.md, rules, definition of done and where to look.
nutrient-dws-client-typescript CLAUDE.md
Instructions for PSPDFKit-labs/nutrient-dws-client-typescript: Canonical agent instructions live in @AGENTS.md — read it first.
jsignpdf AGENTS.md
AGENTS.md instructions for intoolswetrust/jsignpdf, covering agents.md - jsignpdf, project overview, build commands, module structure and key documentation artifacts.