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/agentsnpx skills add SimplePDF/simplepdf-embed --skill agentsgit clone --depth 1 https://github.com/SimplePDF/simplepdf-embedWhat 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.00074 | $0.01360 |
| Opus 5 | $0.00037 | $0.00680 |
| Sonnet 5 | $0.00015 | $0.00272 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade B, and why
edit-pdf scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
response = requests.post("https://agents.simplepdf.com", files={"file": f}) Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://agents.simplepdf.com \ How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SimplePDF - PDF Editor
Edit and fill PDF documents directly in the browser. Add text, signatures, checkboxes, images, and more.
From a URL
For public PDF URLs, use GET with the URL as a query parameter:
GET https://agents.simplepdf.com?url=https://example.com/form.pdf
For signed or sensitive URLs (e.g. presigned S3 links), use POST with a JSON body to keep the URL out of logs and browser history:
curl -X POST https://agents.simplepdf.com \
-H "Content-Type: application/json" \
-d '{"url": "https://s3.amazonaws.com/bucket/doc.pdf?X-Amz-Signature=..."}'
Both return JSON with the editor URL and embed snippets.
From a file
Upload a PDF file to the API. For security and privacy, the file is stored temporarily (24 hours) then automatically deleted. The user has 24 hours to open the link. Once opened, the PDF is loaded into the browser and processed entirely client-side, so the tab can stay open indefinitely.
Shell
curl -X POST https://agents.simplepdf.com -F [email protected]
TypeScript
const form = new FormData();
form.append("file", new Blob([pdfBytes], { type: "application/pdf" }), "document.pdf");
const response = await fetch("https://agents.simplepdf.com", { method: "POST", body: form });
const { url } = await response.json();
Python
import requests
with open("document.pdf", "rb") as f:
response = requests.post("https://agents.simplepdf.com", files={"file": f})
url = response.json()["url"]
Presenting the result to the user
Always present the url field as a clickable link. This is the primary way users will open the editor.
If you have access to a browser automation tool (e.g. agent-browser, Playwright, chrome-devtools MCP server), offer to open the url directly so the user can edit the PDF without leaving the conversation.
The iframe and react fields are for developers embedding the editor in a web application. Only present these when the user is building a web app.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 160 lines · 74 tokens per session scan B 9fc8959b62eb
edit-pdf is a skill published in the GitHub repository SimplePDF/simplepdf-embed (410 stars, last pushed 20d ago), licensed MIT. It adds 74 tokens to every session and 1,360 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
menu-visibility
Track which react-horizontal-scrolling-menu items are on screen: useIsVisible(itemId | 'first' | 'last', defaultValue), useLeftArrowVisible/useRightArrowVisible, the options prop (ratio, rootMargin, threshold), items.getVisible()/subscribe/unsubscribe, and the async IntersectionObserver truth model (items must be seen…
menu-interactions
Wire mouse, wheel and touch input for react-horizontal-scrolling-menu: onWheel/onScroll are plain (api, event) => void callbacks, while ALL mouse/touch props (onMouseDown, onMouseUp, onMouseMove, onMouseLeave, onTouchStart, onTouchMove, onTouchEnd) are handler factories (api) => (event) => void. Covers mouse…
menu-migration
Detect and upgrade pre-v8 react-horizontal-scrolling-menu patterns that agents trained on older data still generate: destructured visibleElements/isFirstItemVisible/isLastItemVisible/initComplete (removed v6), Separator items, separatorClassName and getPrevItem/getNextItem (removed v7), the Arrows prop (removed v3)…
menu-recipes
Recipes composed on the react-horizontal-scrolling-menu public API — NOT props: autoplay (setInterval + scrollNext gated on menuVisible), infinite loop/carousel (clone head/tail + scrollLeft teleport at seams), center on click (scrollToItem 'center'), save/restore scroll position (onUpdate, onInit, scrollContainer)…
menu-setup
Build a working react-horizontal-scrolling-menu: install, the mandatory 'react-horizontal-scrolling-menu/dist/styles.css' import, ScrollMenu with a unique itemId per child, arrow components via VisibilityContext with useLeftArrowVisible/useRightArrowVisible, Header/Footer slots, and CSS customization (fixed item…
menu-testing-ssr
Server rendering and testing for react-horizontal-scrolling-menu: the library is client-only ('use client' required in React Server Components, else "createContext is not a function"), SSR first paint is controlled by the useIsVisible defaultValue argument (canonical ('first', true) / ('last', false))…