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 ulises-jeremias/agent-toolkit --skill docs-generatorgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/docs-generator)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/docs-generator"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/docs-generator.svg" alt="Measured on agentmods" 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 Rogue Agent · line 31 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00044 | $0.01083 |
| Opus 5 | $0.00022 | $0.00541 |
| Sonnet 5 | $0.00009 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00108 |
Grade A, and why
docs-generator 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 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.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docs Generator (WHAT)
Generate or refresh documentation from the actual code, schema, and git history. Never invent — always derive from evidence in the repo.
When to use
- README is missing, stale, or doesn't reflect the current stack
- CHANGELOG needs to be generated from merged PRs or git log
- API spec (OpenAPI/GraphQL) exists but human-readable docs don't
- New repo needs an AGENTS.md to onboard AI assistants
Out of scope
- Does NOT write code — documentation only
- Does NOT commit or push — delegate to
github-cli-workflow - Does NOT update external systems (Confluence, Notion) — use their respective skills
Workflow
README.md generation
- Inspect repo:
package.json/pyproject.toml/Cargo.tomlfor name, description, stack - Read
Makefile/justfile/package.json scriptsfor commands - Read
.github/workflows/for CI structure - Draft README with: Purpose, Stack, Prerequisites, Quick Start, Development, Testing, Contributing
- Apply
output-handshakebefore writing
CHANGELOG.md generation
# Conventional commits format
git log --oneline --no-merges --pretty="format:%h %s" $(git describe --tags --abbrev=0)..HEAD
# Group by type: feat / fix / docs / chore / refactor / perf / test
# Format: ## [Unreleased] with subsections per type
Draft changelog section and ask user to confirm version before finalizing.
API reference generation
- OpenAPI spec → readable endpoint table with params, responses, auth
- GraphQL schema → type reference with fields and descriptions
- Always note the spec version and date in the generated doc
AGENTS.md starter
Use the template from ~/.local/share//skills-catalog.yaml patterns:
- Purpose and stack
- Repository inspection order
- What AI assistants may and must not do
- Key commands (build, test, lint)
- Links to key docs
Inline Documentation (why, not what) — per addyosmani/agent-skills documentation-and-adrs 2026-08-12 diff docs/research/diff-394-documentation-and-adrs.md
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 · 121 lines · 44 tokens per session scan A af8059a9aa96
docs-generator is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 44 tokens to every session and 1,083 once invoked, about $0.0002 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-09-04.
Other skills, from other repositories
release-governance
Use when preparing, auditing, releasing, PDF-hardening, or rebuttal-hardening academic manuscripts, datasets, artifacts, reviewer packets, or claim registers involving multiple refs, local assets, human labels, agent-assisted drafts, wide tables, figure provenance, submission PDFs, or evidence-boundary checks.
read
Read PDF page by page with structured output — key arguments, terms glossary, thesis connections. Use when reading academic papers, books, or articles.
PDF → spreadsheet — extract data into Excel (Local MCP)
Use when the user wants to pull data out of one or more PDFs (invoices, bank/credit-card statements, receipts, reports, tables) and put it into a spreadsheet. pdfread is one of the most-used tools; this codifies the read-PDF → structure → write-Excel workflow. Powered by Local MCP, on-device.
onepage-pdf
A tool that converts an HTML page into one continuous PDF page without normal page breaks. It preserves the desktop layout, backgrounds, and selectable text.
omh-report-package
This is a Hermes-native report-package workflow skill.
slides
Create and edit presentation slide decks (.pptx) with PptxGenJS, bundled layout helpers, and render/validation utilities. Use when tasks involve building a new PowerPoint deck, recreating slides from screenshots/PDFs/reference decks, modifying slide content while preserving editable output, adding…