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/intoolswetrust/jsignpdf/agents-mdgit clone --depth 1 https://github.com/intoolswetrust/jsignpdfWhat 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.02704 | $0.02704 |
| Opus 5 | $0.01352 | $0.01352 |
| Sonnet 5 | $0.00541 | $0.00541 |
| Haiku 4.5 | $0.00270 | $0.00270 |
Grade A, and why
jsignpdf 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 144 lines · 2,704 tokens per session scan A 7e424d8db9f5
jsignpdf AGENTS.md is an instructions file published in the GitHub repository intoolswetrust/jsignpdf (466 stars, last pushed 3d ago), with no licence file. It adds 2,704 tokens to every session, about $0.0135 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-30.
Other instructions, from other repositories
fx2048 copilot-instructions.md
Copilot instructions for brunoborges/fx2048, covering copilot instructions for fx2048, build and run commands, architecture and codebase conventions.
pdfnative-mcp AGENTS.md
Instructions for Nizoka/pdfnative-mcp, covering agents.md — pdfnative-mcp, 1. tool catalogue (28 tools), 2. decision tree, 3. token-frugal responses and 4. output modes & environment.
pdfnative-mcp CLAUDE.md
Instructions for Nizoka/pdfnative-mcp, covering claude.md, what this is, commands, architecture map and non-negotiable conventions.
pdfnative-mcp copilot-instructions.md
Instructions for Nizoka/pdfnative-mcp, covering pdfnative-mcp - project guidelines, architecture (one line each), core conventions, quality gate (all prs) and release process.
pdfnative-mcp mcp-server.instructions.md
Use when editing MCP transport, tool registration, JSON schemas, or request/response handling.
pdfnative-mcp security.instructions.md
Use when touching file IO, path handling, or sensitive key/certificate inputs.