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 jdrhyne/agent-skills --skill nudocsgit clone --depth 1 https://github.com/jdrhyne/agent-skillsWrote 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/jdrhyne/agent-skills/nudocs)<a href="https://agentmods.dev/skills/jdrhyne/agent-skills/nudocs"><img src="https://agentmods.dev/badge/skills/jdrhyne/agent-skills/nudocs/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/jdrhyne/agent-skills/nudocs"><img src="https://agentmods.dev/badge/skills/jdrhyne/agent-skills/nudocs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 41 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.
- medium Excessive Agency · line 77 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.00083 | $0.01313 |
| Opus 5 | $0.00042 | $0.00656 |
| Sonnet 5 | $0.00017 | $0.00263 |
| Haiku 4.5 | $0.00008 | $0.00131 |
Grade A, and why
nudocs 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 11d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nudocs
Use the authenticated Nudocs CLI to upload documents for hosted editing, retrieve private edit links, list or export documents, and delete a specific remote document.
Setup without exposing credentials
Inspect nudocs --help and nudocs config --help before setup because authentication UX can change by version.
Use one authentication method, not both:
- Interactive personal setup: if the current CLI exposes an interactive login/config flow, complete it in the user's terminal. Otherwise have the user enter the key directly in a protected local editor or secret manager, outside the agent transcript. Keep
~/.config/nudocsmode0700and its API-key file mode0600. - Protected environment setup: use
NUDOCS_API_KEYonly when it is already supplied through protected local or CI secret storage.
Never ask the user to paste the key into chat, put it in a command argument, echo it into a file, display it with nudocs config, or print environment/config contents. Verify authentication through behavior such as a bounded nudocs list, not by inspecting the secret.
Discover the installed CLI contract
Before an operation, inspect the relevant current help:
nudocs --help
nudocs upload --help
nudocs link --help
nudocs pull --help
nudocs delete --help
The maintained CLI currently documents upload, list, link, pull, delete, and config. Do not invent aliases or use the obsolete gimme command.
For current upload/export formats, read references/formats.md. Do not load that reference for listing, link lookup, or deletion. Service limits are account- and time-dependent: use the CLI/API response or current Nudocs account UI instead of a hard-coded document count.
Operation contract
Exact document identity
Every link, pull, and delete workflow must resolve and pass one exact document ID returned by the current nudocs list output or explicitly supplied by the user:
nudocs link <document-id>
nudocs pull <document-id> --format <format> --output <exact-output-path>
nudocs delete <document-id>
What ships with it
6 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.
- 11d ago First seen · 119 lines · 83 tokens per session scan A 964e70bac856
nudocs is a skill published in the GitHub repository jdrhyne/agent-skills (241 stars, last pushed 11d ago), licensed MIT. It adds 83 tokens to every session and 1,313 once invoked, about $0.0004 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-30.
Other skills, from other repositories
ospec
Document-driven OSpec workflow for initialization, change/goal routing, validation, archiving, and durable project knowledge.
openakita/skills@doc-coauthoring
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, PRDs, RFCs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works…
openakita/skills@docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of "Word doc", "word document", ".docx", or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when…
openakita/skills@ppt-creator
Create professional presentations using the Pyramid Principle methodology. Supports PPTX generation, Marp/Reveal.js Markdown slides, chart creation, speaker notes, and self-evaluation rubrics. Minimal intake form to rapid output workflow.
openakita/skills@pptx
Use this skill any time a .pptx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying…
openakita/skills@xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…