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 skills add PIXARTSeu/Synapse --skill file-handlinggit clone --depth 1 https://github.com/PIXARTSeu/SynapseWrote 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/pixartseu/synapse/file-handling)<a href="https://agentmods.dev/skills/pixartseu/synapse/file-handling"><img src="https://agentmods.dev/badge/skills/pixartseu/synapse/file-handling.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.00058 | $0.03356 |
| Opus 5 | $0.00029 | $0.01678 |
| Sonnet 5 | $0.00012 | $0.00671 |
| Haiku 4.5 | $0.00006 | $0.00336 |
Grade A, and why
file-handling scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
await fetch(url, { method: 'PUT', body: file, headers: { 'Content-Type': file.type } }) The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 437 lines · 58 tokens per session scan A 5f0430f6ec8f
file-handling is a skill published in the GitHub repository PIXARTSeu/Synapse (9 stars, last pushed 12d ago), with no licence file. It adds 58 tokens to every session and 3,356 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
cc-api-design-safety
A safety guide for designing REST API responses and creating downstream files such as Excel, CSV, PDF, or reconciliation files.
document-skills
Professional document creation, editing, and analysis for Office formats (docx, pdf, pptx, xlsx). Use when working with Word documents, PDFs, PowerPoint presentations, or Excel spreadsheets.
backend-report-generation
Enforce report generation patterns including PDF generation (Puppeteer, wkhtmltopdf), Excel/CSV export, async generation with queues, report scheduling, large dataset handling, template rendering, and report API design. NOT for real-time dashboards or live charting.
dev-document
Document generation (PDF, DOCX, XLSX, PPTX). Trigger when the user wants to create a document, generate a report, export to PDF/Word/Excel/PowerPoint, or produce an office file.
cc-streaming-export-safety
A safety workflow for user-triggered exports or batch serialization of large Excel, CSV, JSON, JSONL, or PDF files.
streaming-export-safety
A safety guide for exporting large Excel, CSV, JSON, or PDF files. It also covers converting many records and building large data objects in memory.