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/releasegit 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.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.00379 | $0.00379 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
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 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.
What it actually says
Release Note Standards
Structure
- One file per release: release-notes/vX.Y.Z.md
- Keep sections ordered and omit empty sections.
- Use conventional prefixes in bullets: feat(scope), fix(scope), chore(scope), docs(scope), ci(scope).
Required parity
- CHANGELOG entry must mirror release bullets.
- GitHub Release body should come from release-notes/vX.Y.Z.md.
- Include compatibility statement for patch/minor releases.
Publication flow
- Write release-notes/vX.Y.Z.md.
- Mirror into CHANGELOG.md.
- Bump package version.
- Run the quality gate (
examples:checkruns as part oftest:coveragein CI — keep it green). - Tag vX.Y.Z.
- Publish GitHub Release.
- Let publish workflow publish to npm via OIDC.
Pre-publish dry run & rollback
- Dry run the registry payload before tagging:
npx -y @modelcontextprotocol/publisher@latest validate server.json(or the repo'smcp-publishstep) to catchname/version drift early. - npm: Trusted Publishing runs from the tag — do not publish manually. If a
bad version ships, do not unpublish; cut a superseding patch (vX.Y.Z+1) and,
if within npm's 72 h window and truly broken,
npm deprecate [email protected] "use X.Y.Z+1". - Tags are immutable once released. A mistake = new patch tag, never a force-moved tag.
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 · 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 10d ago), licensed MIT. It adds 379 tokens to every session, about $0.0019 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
codex-ppt-skill AGENTS.md
Instructions for ningzimu/codex-ppt-skill, covering agents.md, contribution flow, changelog, release process and verification.
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).
best-claude-hud AGENTS.md
Instructions for GaoSSR/best-claude-hud, covering project agent instructions and release work.
cetus AGENTS.md
Instructions for drewnekota/cetus, covering repository instructions and releases.
OpenMicro AGENTS.md
Instructions for stephenleo/OpenMicro, covering openmicro — project conventions and releases.
claude-code-hubs CLAUDE.md
Instructions for pigfoot/claude-code-hubs, covering plugin version management, for each plugin (e.g., nano-banana), checklist template, 1. update plugin.json and 2. update readme.md - add new section at top.