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 agentmods add skills/tomzx/agents/create-documentationnpx skills add tomzx/agents --skill create-documentationgit clone --depth 1 https://github.com/tomzx/agentsWhat 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 | $0.00029 | $0.00754 |
| Opus 5 | $0.00015 | $0.00377 |
| Sonnet 5 | $0.00006 | $0.00151 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
create-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 yesterday.
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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Documentation
Produces documentation for a feature or component organized according to the Divio documentation framework: tutorials, how-to guides, reference, and explanations.
For detailed Divio guidance (DO/DON'T lists, decision trees, per-type structures), consult the divio-documentation skill. This skill focuses on the production workflow: deciding which types to write and producing the output.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - If no argument is provided, locate the feature directory under
.sdlc/features/whose frontmatterissuefield references$ISSUE_NUMBER. - Feature or component description provided in context or as
$1 - Access to the codebase, specification, or implementation (if available)
Steps
- Understand the feature: what it does, who uses it, and common use cases.
- Identify which documentation types are needed (use the decision tree in
divio-documentationif unsure). - Follow the DO/DON'T rules and structure templates from
divio-documentationfor each type. - Write a tutorial if users need onboarding guidance.
- Write how-to guides for the most common user tasks.
- Write reference documentation for all public APIs, config options, and interfaces.
- Write an explanation section if the design or behavior needs conceptual context.
- Cross-link between types but keep their boundaries clean.
- Write the documentation to
.sdlc/features/N-<slug>/documentation.md, creating the directory if it does not exist.
Output Format
Use the template at skills/sdlc/templates/features/documentation.md (copied to .sdlc/templates/features/documentation.md by /initialize-sdlc-directory; use the project's customized copy if present). Write the result to the artifact path named in the steps above.
Outcome
If $OUTCOME_YAML is set, emit verdict: approved there per skills/sdlc/references/shared.md, mirroring the status: draft written to the artifact. If the artifact could not be produced, omit the file.
In the same emission, list the artifact under artifacts: (.sdlc/features/N-<slug>/documentation.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.
- yesterday First seen · 65 lines · 29 tokens per session scan A 6734d3e358fa
create-documentation is a skill published in the GitHub repository tomzx/agents (5 stars, last pushed 4d ago), licensed MIT. It adds 29 tokens to every session and 754 once invoked, about $0.0001 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-31.
Other skills, from other repositories
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
a-evolve
Apply A-Evolve's agentic evolution methodology to improve AI agent performance across runs. Use when the user wants to diagnose agent failures, generate targeted skills from error patterns, evolve system prompts, or accumulate episodic knowledge. Works standalone or inside AutoResearchClaw pipelines. Triggers on…
hive.chart-creation-foundations
Required reading whenever any chart tool is available. Teaches the one-tool embedding contract (call chartrender → live chart appears in chat AND a downloadable PNG lands in the queen session dir), the ECharts (data viz) vs Mermaid (structural diagrams) decision, the BI/financial-grade aesthetic baseline (no…
📝 任务完成后归档
重要提醒: 每次完成复杂调试或开发任务后，主动执行此流程！ 将学到的经验归档为 skill，供以后参考。不要等用户提醒。.
deck-course-module
暖纸背景 + Playfair, 左侧学习目标常驻, 含 MCQ 自测页.
code-documenter
Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.