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 automateyournetwork/netclaw --skill document-generationgit clone --depth 1 https://github.com/automateyournetwork/netclawWrote 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/automateyournetwork/netclaw/document-generation)<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/document-generation"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/document-generation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/automateyournetwork/netclaw/document-generation"><img src="https://agentmods.dev/badge/skills/automateyournetwork/netclaw/document-generation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 20 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00118 | $0.01911 |
| Opus 5.5 | $0.00047 | $0.00764 |
| Sonnet 5.5 | $0.00024 | $0.00382 |
| Haiku 4.5 | $0.00012 | $0.00191 |
Grade A, and why
document-generation 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 29d 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 — 136 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Document Generation
MCP Server
- Server:
document-mcp(NetClaw-authored, spec 082 / roadmap R18) - Command:
$DOCUMENT_MCP_CMD - Transport: stdio
- Credentials: none. This server writes files and touches nothing else
- Infrastructure: no device access, no ticket writes — so there is no approval gate here
The one rule that matters most
A document must never fabricate to fill a blank.
Tool output is ephemeral — read once, in context, by the person who asked. A document is not. It gets emailed, attached to a ticket, filed for audit, and read months later by someone who was not there, and it carries the authority of its formatting.
A professional-looking change record with a plausible invented number is a far more effective way to launder
a guess into an official record than any amount of terminal output, because nobody re-derives a figure
that is already in a table in a .docx.
So: never infer, estimate, interpolate, or carry forward a stale value to complete a document. If you do
not have a figure, send {"unavailable": "<why>"}. The server renders that as visible text. It will not
render a blank, and it will not let you send one.
Tagged values — the only accepted shape
Every value in a figure, table, keyvalue or form field is one of exactly three shapes:
{"v": "fgt-01", "src": "fgt_system_status", "device": "fgt-01", "as_of": "2026-08-03T13:58:00Z"}
{"unavailable": "device did not answer within timeout"}
{"failed": "FortiGate plane unreachable: connection refused"}
| You send | The document shows |
|---|---|
{"v": x, "src": ...} |
x, with a visible source |
{"v": ""} |
(empty) — the source was consulted and returned nothing |
{"unavailable": r} |
NOT AVAILABLE — r |
{"failed": r} |
RETRIEVAL FAILED — r |
{"v": x} with no src |
refused |
a bare x |
refused |
unavailable and failed are different facts and render differently: a dead query is not an empty result.
Neither ever renders as N/A, 0, -, or an empty cell.
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.
- 29d ago Changed · +27 tokens per session 7bb2d8fa8a34
- 1mo ago First seen · 136 lines · 91 tokens per session scan A 2f6f16032063
document-generation is a skill published in the GitHub repository automateyournetwork/netclaw (684 stars, last pushed yesterday), licensed Apache-2.0. It adds 118 tokens to every session and 1,911 once invoked, about $0.0005 per session on Opus 5.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
document-processing-expert
Read, generate and modify office documents and PDFs from code: PDF extraction and forms, Word documents, Excel workbooks and PowerPoint decks. Use when the user mentions PDF, DOCX, XLSX, PPTX, Word, Excel, PowerPoint or spreadsheets, wants data extracted from documents, needs a report or invoice generated as a file…
document-creator
Use when creating, editing, and generating Office documents programmatically — Word, PowerPoint, Excel, and PDF. One interface for all document formats with shared methodology.
office-artifacts
Manage Office files, formats and versions; use Writer, Calc or Impress for content.
brand-xlsx
Brand-aware Excel engine. Use to (1) EXTRACT a company's brand from a .xlsx template into a reusable "Brand Profile", (2) COMPREHEND the template with the model (optional), (3) VERIFY it, (4) GENERATE a new on-brand .xlsx from a GridDocument fill manifest. Trigger on "extract our brand", "use our workbook template"…
document-processing
End-to-end document processing agent skill covering PDF manipulation (extract, merge, split, rotate, watermark, form-fill, OCR), DOCX creation and editing (templates, mail-merge, style management), XLSX spreadsheet handling (formulas, charts, pivot tables, data analysis), PPTX presentation generation (layouts, charts…
office-router
Route Office requests into the correct xlsx, docx, or pptx workflow, while preferring Slidev for new presentation drafts unless .pptx is explicitly required.