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 chandrudp29/skillhub --skill doc-generatorgit clone --depth 1 https://github.com/chandrudp29/skillhubWrote 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/chandrudp29/skillhub/doc-generator)<a href="https://agentmods.dev/skills/chandrudp29/skillhub/doc-generator"><img src="https://agentmods.dev/badge/skills/chandrudp29/skillhub/doc-generator/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/chandrudp29/skillhub/doc-generator"><img src="https://agentmods.dev/badge/skills/chandrudp29/skillhub/doc-generator.svg" alt="Reviewed on agentmods" width="80" 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.00044 | $0.01060 |
| Opus 5.5 | $0.00018 | $0.00424 |
| Sonnet 5.5 | $0.00009 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
doc-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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc Generator
Generates documentation that developers actually read and use — not boilerplate that everyone ignores.
When to Use
- "Write a README for this project"
- "Add docstrings to these functions"
- "Generate API documentation"
- "Write a changelog entry for this release"
- Before open-sourcing or sharing any code
README Generation
A README answers these questions in this order:
1. What is this? (one sentence) Not "a powerful, flexible, enterprise-grade solution" — what does it actually do?
2. Why would I use this? (one paragraph) What problem does it solve? What's the alternative? When should I NOT use it?
3. How do I install it? (one command)
pip install yourpackage
4. How do I use it? (minimal working example) The simplest thing that works, copy-pasteable, tested:
from yourpackage import Thing
result = Thing().do_something("input")
print(result) # "expected output"
5. Full API / configuration reference Only after the quick example. Developers who need it will scroll; those who don't won't be overwhelmed.
6. Contributing / Development setup How to run tests, how to open a PR.
README Template
# project-name
One sentence: what it does.
## Install
\`\`\`bash
pip install project-name
\`\`\`
## Quick Start
\`\`\`python
[minimal working example]
\`\`\`
## Why project-name?
[problem it solves, who it's for, what makes it different]
## Usage
[fuller examples and configuration]
## API Reference
[function signatures and descriptions]
## Contributing
[how to set up dev environment, run tests, open PRs]
## License
MIT
Docstring Generation
Write docstrings that explain WHY and WHAT, not HOW (the code shows how):
Good:
def chunk_text(text: str, max_tokens: int = 512, overlap: int = 50) -> list[str]:
"""
Split text into overlapping chunks for RAG ingestion.
Overlap prevents context loss at chunk boundaries — a sentence split
across two chunks is still fully recoverable during retrieval.
Args:
text: The document text to split. Handles Unicode correctly.
max_tokens: Target chunk size. Actual chunks may be slightly larger
to avoid splitting mid-sentence.
overlap: Tokens of overlap between consecutive chunks.
Returns:
List of text chunks, ordered by position in the original text.
Raises:
ValueError: If max_tokens < overlap.
"""
What ships with it
1 file 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.
- 1mo ago First seen · 161 lines · 44 tokens per session scan A e2cba61494d8
doc-generator is a skill published in the GitHub repository chandrudp29/skillhub (14 stars, last pushed 3mo ago), licensed MIT. It adds 44 tokens to every session and 1,060 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
documentation-writer
Write clear technical documentation including READMEs, API docs, architecture guides, and inline documentation. Use when creating or improving project documentation.
documentation-and-adrs
Use this skill when you need to record an architecture decision (ADR) or document the reasoning behind a design choice — when changing public APIs, shipping features that change behavior, or recording context that future engineers (human or agent) will need to understand the codebase. Does NOT replace code comments or…
atlas-changelog
Maintain per-repo and cross-repo changelogs — append structured entries after agent work. Use when asked to "log this change", "update changelog", "what changed", "change history".
document-writer
Write or update technical documentation grounded in the real codebase. Use when the user asks for README, API docs, architecture guides, user guides, CONTRIBUTING docs, migration notes, or JSDoc/code comments, or wants technical docs rewritten into natural Chinese with correct terminology. Not for general prose…
write-readme
Generates or updates a README.md for a project or package. Reads the source code to understand the project and produces a clear, accurate README following the project's conventions. Invoked when the user asks to write, update, or generate a README.
write-changelog
Generates a CHANGELOG.md entry for a release by summarizing git commits since the last tag. Groups changes by type: Added, Changed, Fixed, Removed. Follows Keep a Changelog format (https://keepachangelog.com). Invoked when the user asks to update the changelog, write release notes, or prepare a release.