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 skills/simplepdf/simplepdf-embed/build-with-simplepdfnpx skills add SimplePDF/simplepdf-embed --skill build-with-simplepdfgit clone --depth 1 https://github.com/SimplePDF/simplepdf-embedWrote 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/skills/simplepdf/simplepdf-embed/build-with-simplepdf)<a href="https://agentmods.dev/skills/simplepdf/simplepdf-embed/build-with-simplepdf"><img src="https://agentmods.dev/badge/skills/simplepdf/simplepdf-embed/build-with-simplepdf.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.1 | $0.00103 | $0.06113 |
| Opus 5 | $0.00051 | $0.03057 |
| Sonnet 5 | $0.00021 | $0.01223 |
| Haiku 4.5 | $0.00010 | $0.00611 |
Grade A, and why
build-with-simplepdf 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.
How it starts
The opening of the file, as written. The whole thing — 403 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Build with SimplePDF
You are guiding and implementing a SimplePDF integration in an existing application.
Four ways to use SimplePDF, freely combinable (a strong intake workflow often prefills first and adds live agentic help second):
- Human-driven embed — viewer/editor inside the product.
- Programmatic control — application code controls the live editor.
- Live agentic control — an LLM calls tools that execute against the live editor in the browser.
- Prefill + human review — an agent/backend prepares field values before the PDF opens, then a person reviews, corrects, signs and submits.
Core product principle: human-in-the-loop
An agent may read fields and document content when permitted, suggest or set values, navigate, focus fields, open tools, prefill from known data, and explain what is missing. Final review, correction, signing/attestation and submission stay with the human by default. Never design autonomous submission merely because submit() exists; if the user explicitly wants it, clarify the requirement and warn that human-in-the-loop is safer for applications, regulated forms and attestations.
Interaction rules
- ONE question per reply — then STOP and wait for the answer. If a step needs several answers, ask the first and hold the rest. Previewing future questions ("once you tell me X, I'll need Y") counts as asking them; so does a bulleted list of things to confirm. The only exception is a clarifying restatement of the same question. If you catch yourself drafting more than one question, delete everything after the first.
- Never narrate this skill or its process. No "per the skill", "one question at a time", no route or phase names. The user should experience a senior engineer pairing with them, not a script being followed.
- Use
AskUserQuestionfor choices when it is available: 2–4 concrete options, neutrally worded and neutrally ordered — never mark an option "(Recommended)" and never steer through ordering; put trade-offs and cautions in the option descriptions instead. Include an "Other / not sure" path when useful. Keep header chips under 12 chars. Free-text answers (e.g. thecompanyIdentifier) use a plain question. WithoutAskUserQuestion, ask the same single question as concise text. - Keep replies short: a sentence or two plus the one question. No front-loaded plans or prerequisites, no recaps of what the user just said. Match their energy: terse if they're terse, warmer if they're chatty.
- Never ask a question the repository or the user's own words already answer. State what you found and move on.
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 · 403 lines · 103 tokens per session scan A 7148d5f541b3
build-with-simplepdf is a skill published in the GitHub repository SimplePDF/simplepdf-embed (409 stars, last pushed 2d ago), licensed MIT. It adds 103 tokens to every session and 6,113 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
PDF Form Filler
Fill out PDF forms programmatically and extract form data.
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and…
ck:pdf
Extract text/tables, create, merge, split PDFs. Fill PDF forms programmatically. Use for PDF processing, generation, form filling, document analysis, batch operations.
pydicom
Use pydicom to read, inspect, write, transform, and safely preflight local DICOM datasets and pixel data. Applies to DICOM metadata, transfer syntaxes, compression plugins, frames, private elements, JSON, and bounded de-identification review.
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.