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 willvelida/code-minions --skill creating-documentationgit clone --depth 1 https://github.com/willvelida/code-minionsWrote 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/willvelida/code-minions/creating-documentation)<a href="https://agentmods.dev/skills/willvelida/code-minions/creating-documentation"><img src="https://agentmods.dev/badge/skills/willvelida/code-minions/creating-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/willvelida/code-minions/creating-documentation"><img src="https://agentmods.dev/badge/skills/willvelida/code-minions/creating-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.00060 | $0.00693 |
| Opus 5.5 | $0.00024 | $0.00277 |
| Sonnet 5.5 | $0.00012 | $0.00139 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
creating-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 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Documentation
Overview
This skill provides capabilities for creating and reviewing README files and other repository documentation that follows established best practices for structure, accessibility, and user experience.
Good documentation is the front door to your project. It helps users understand what your project does, how to use it, and how to contribute. This skill ensures documentation is clear, accessible, and follows industry standards.
Capabilities
| Capability | Action | Description |
|---|---|---|
| Create README | actions/create-readme.md |
Generate a comprehensive README for a repository |
| Create CONTRIBUTING | actions/create-contributing.md |
Generate contribution guidelines |
| Review | actions/review-documentation.md |
Analyse existing documentation for quality and accessibility |
Standards
This skill bundles the following standards in standards/:
| Standard | File | Description |
|---|---|---|
| README Structure | readme-structure.md |
Essential sections and organization for README files |
| Accessibility | accessibility.md |
Accessibility requirements for inclusive documentation |
| Writing Style | writing-style.md |
Plain language and readability guidelines |
| Markdown | markdown.md |
Markdown formatting best practices |
| Checklist | checklist.md |
Consolidated compliance and quality checklist |
Principles
1. Audience First
Write for your audience. A README's primary purpose is to help visitors quickly understand your project and get started. Don't assume prior knowledge—provide context and links for unfamiliar concepts.
2. Progressive Disclosure
Present information in order of importance:
- Title & Description: What is this project? (immediate)
- Installation & Usage: How do I use it? (primary)
- Contributing & License: How can I help? (secondary)
3. Accessibility Matters
Documentation should be accessible to all users:
- Use proper heading hierarchy (don't skip levels)
- Provide alt text for all images
- Write descriptive link text (not "click here")
- Use plain language and short sentences
What ships with it
8 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.
- 1mo ago First seen · 75 lines · 60 tokens per session scan A 24f2509061b1
creating-documentation is a skill published in the GitHub repository willvelida/code-minions (23 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 693 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.