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 KunanonJ/ai-skills-hub --skill documentationgit clone --depth 1 https://github.com/KunanonJ/ai-skills-hubWrote 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/kunanonj/ai-skills-hub/documentation)<a href="https://agentmods.dev/skills/kunanonj/ai-skills-hub/documentation"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/documentation/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/kunanonj/ai-skills-hub/documentation"><img src="https://agentmods.dev/badge/skills/kunanonj/ai-skills-hub/documentation.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.00022 | $0.01356 |
| Opus 5 | $0.00011 | $0.00678 |
| Sonnet 5 | $0.00004 | $0.00271 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
documentation 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 9d 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.
This is a copy
94% identical to documentation — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Workflow Bundle
Overview
Comprehensive documentation workflow for generating API documentation, architecture documentation, README files, code comments, and technical content from codebases.
When to Use This Workflow
Use this workflow when:
- Creating project documentation
- Generating API documentation
- Writing architecture docs
- Documenting code
- Creating user guides
- Maintaining wikis
Workflow Phases
Phase 1: Documentation Planning
Skills to Invoke
docs-architect- Documentation architecturedocumentation-templates- Documentation templates
Actions
- Identify documentation needs
- Choose documentation tools
- Plan documentation structure
- Define style guidelines
- Set up documentation site
Copy-Paste Prompts
Use @docs-architect to plan documentation structure
Use @documentation-templates to set up documentation
Phase 2: API Documentation
Skills to Invoke
api-documenter- API documentationapi-documentation-generator- Auto-generationopenapi-spec-generation- OpenAPI specs
Actions
- Extract API endpoints
- Generate OpenAPI specs
- Create API reference
- Add usage examples
- Set up auto-generation
Copy-Paste Prompts
Use @api-documenter to generate API documentation
Use @openapi-spec-generation to create OpenAPI specs
Phase 3: Architecture Documentation
Skills to Invoke
c4-architecture-c4-architecture- C4 architecturec4-context- Context diagramsc4-container- Container diagramsc4-component- Component diagramsc4-code- Code diagramsmermaid-expert- Mermaid diagrams
Actions
- Create C4 diagrams
- Document architecture
- Generate sequence diagrams
- Document data flows
- Create deployment docs
Copy-Paste Prompts
Use @c4-architecture-c4-architecture to create C4 diagrams
Use @mermaid-expert to create architecture diagrams
Phase 4: Code Documentation
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.
- 9d ago First seen · 266 lines · 22 tokens per session scan A 997e58cd56e9
documentation is a skill published in the GitHub repository KunanonJ/ai-skills-hub (5 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,356 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to documentation, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
writing-tests
Write unit tests, component tests, and integration tests for AiderDesk using Vitest and React Testing Library. Use when creating new tests, adding test coverage, configuring mocks, setting up test files, or debugging failing tests.
confirm-failures-are-causally-linked-to-the-task-before-reportin
When delegating a task affected by this skill, include.
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
run-tests-on-the-unmodified-codebase-before-starting-to-establis
When delegating a task affected by this skill, include.
coding-standards
A set of general coding standards and practical patterns for TypeScript, JavaScript, React, and Node.js. It covers readable naming, simple designs, avoiding repetition, and delaying unnecessary features.
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.