Borrowing it
Nothing to install: this file belongs to Nizoka/pdfnative-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/Nizoka/pdfnative-mcp/main/.github/instructions/release.instructions.mdgit 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/release)<a href="https://agentmods.dev/instructions/nizoka/pdfnative-mcp/release"><img src="https://agentmods.dev/badge/instructions/nizoka/pdfnative-mcp/release/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/nizoka/pdfnative-mcp/release"><img src="https://agentmods.dev/badge/instructions/nizoka/pdfnative-mcp/release.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.00817 | $0.00817 |
| Opus 5.5 | $0.00327 | $0.00327 |
| Sonnet 5.5 | $0.00163 | $0.00163 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
pdfnative-mcp release.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 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Standards
Structure
- One file per release:
release-notes/vX.Y.Z.md(scaffold:release-notes/TEMPLATE.md). Released notes are read-only history. - The release PR body is drafted at
.github/drafts/pr-vX.Y.Z.mdfromrelease-notes/PR_TEMPLATE.md(committed; the maintainer opens the PR). - Keep sections ordered and omit empty sections.
- Use conventional prefixes in bullets: feat(scope), fix(scope), chore(scope), docs(scope), ci(scope).
- English everywhere. No
Co-Authored-Bytrailer and no mention of an AI assistant in commits, PR bodies or release notes (.claude/settings.jsonattribution.commitis empty).
Required parity
- CHANGELOG entry must mirror release bullets; every
## [X.Y.Z]heading has a compare link (verify:docsrulechangelog-ladder). - GitHub Release body comes from
release-notes/vX.Y.Z.md. - Include a compatibility statement, and an Upgrade section that declares every output change and every rebaselined sample BEFORE publication.
- Every figure quoted (tests, coverage, tools, samples, corpus verdicts) comes from a command run on the release branch — never typed from memory.
docs/assets/ecosystem.jsonis the single source of counts;npm run verify:docsholds the documents to it.
Publication flow
npx tsx scripts/release-prepare.ts --version X.Y.Z— mechanical bump (package.json + lock,src/version.ts,server.json×2,CITATION.cff,SECURITY.md, manifest stamps) and scaffolds. It never bumpsTOOL_API_VERSION: decide that underdocs/API_STABILITY.md§3.- Write
release-notes/vX.Y.Z.md, mirror intoCHANGELOG.md, updateROADMAP.md. npx tsx scripts/gate.ts --publish --require-allwith veraPDF installed (every step, no SKIP).- If output changed on purpose:
npx tsx scripts/verify-samples.ts --update, explain it in the provenance note and the Upgrade section. - Run the
release-auditskill; fix what it confirms. - Write
.github/drafts/pr-vX.Y.Z.md. Stop. The maintainer pushes, opens the PR, tags and publishes.
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 Changed · +5 lines · +438 tokens per session c9e8ec967547
- 1mo ago First seen · 33 lines · 379 tokens per session scan A d164c7e74e9c
pdfnative-mcp release.instructions.md is an instructions file published in the GitHub repository Nizoka/pdfnative-mcp (2 stars, last pushed 7d ago), licensed MIT. It adds 817 tokens to every session, about $0.0033 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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.