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/thewolffish/wolffish-app/documentnpx skills add thewolffish/wolffish-app --skill documentgit clone --depth 1 https://github.com/thewolffish/wolffish-appWrote 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/thewolffish/wolffish-app/document)<a href="https://agentmods.dev/skills/thewolffish/wolffish-app/document"><img src="https://agentmods.dev/badge/skills/thewolffish/wolffish-app/document.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.00024 | $0.02128 |
| Opus 5 | $0.00012 | $0.01064 |
| Sonnet 5 | $0.00005 | $0.00426 |
| Haiku 4.5 | $0.00002 | $0.00213 |
Grade A, and why
document 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 5d 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
Document
Interface
- Tools:
document_read,document_create,document_modify,document_template,document_convert,document_merge,document_toc,document_metadata,document_compare,document_extract_images - Supported input formats: .docx, .html, .md, .txt, .rtf
- Primary output format: .docx (create/modify/merge/template)
- All paths must be absolute. Complex parameters are JSON strings.
Rules
- Use
mammothfor reading .docx files (extracts to HTML/text). - Use
docxnpm package for creating new .docx files programmatically. - For template filling (
document_template), unzip the .docx, string-replace{{placeholders}}in the XML, and rezip. This preserves original formatting. - For
document_convertwith docx->pdf output, this capability uses the pdf capability (declared inrequires). - Support BiDi/RTL text via the docx package's bidirectional paragraph options.
- Use
os.EOLfor line endings in plain text output. - Handle EBUSY/EPERM errors gracefully (file open in another app).
Content Block Types for document_create
heading: { type, text, level (1-6), alignment? }paragraph: { type, text, alignment?, bold?, italic?, font?, size?, spacing?, indent? }table: { type, headers: string[], rows: string[][], columnWidths?, style? }image: { type, path, width?, height?, caption? }list: { type, items: string[], ordered?, nested? }page_break: { type }table_of_contents: { type, depth? }header: { type, text }footer: { type, text }code_block: { type, text, language? }
What ships with it
2 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.
- 5d ago First seen · 275 lines · 24 tokens per session scan A ead82fe5ec20
document is a skill published in the GitHub repository thewolffish/wolffish-app (5 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 2,128 once invoked, about $0.0001 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 skills, from other repositories
doc-ingest
Extract readable text from document files — PDF, XLSX/CSV/TSV, DOCX, PPTX, and plain-text formats — so any task that arrives with an attachment can actually consume it.
agent-computer-use
REQUIRED for any task that involves operating a desktop application — opening apps, clicking buttons, typing into fields, pressing keys, scrolling, dragging, reading what's on screen, moving or resizing windows, or verifying state after an action. Always use the agent-cu CLI commands (open, snapshot, click, type, key…
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.
create-skill
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
logging-and-error-reporting
How and when to log (log:: levels, safe macros) and report errors to Sentry (reporterror!) in the Warp codebase. Use when adding or reviewing any logging or error reporting — picking a log level, deciding log vs. reporterror!, keeping sensitive data out of logs, or surfacing an error to Sentry.
gui-integration-test
GUI desktop app only. Writes, runs, and debugs Warp integration tests using the custom Builder/TestStep framework in crates/integration. Use when adding a new integration test, fixing a failing integration test, wiring a test into the manual runner or nextest suite, or verifying end-to-end UI and terminal behavior in…