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 KylinMountain/nano-claw --skill docs-writergit clone --depth 1 https://github.com/KylinMountain/nano-clawWrote 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/kylinmountain/nano-claw/docs-writer)<a href="https://agentmods.dev/skills/kylinmountain/nano-claw/docs-writer"><img src="https://agentmods.dev/badge/skills/kylinmountain/nano-claw/docs-writer.svg" alt="Measured on agentmods" 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.00011 | $0.00235 |
| Opus 5 | $0.00005 | $0.00118 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
docs-writer 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 8d 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.
What it actually says
Documentation Writer Skill
Purpose
This skill provides specialized guidance for writing high-quality technical documentation, including README files, API documentation, user guides, and code comments.
Guidelines
When activated, follow these documentation best practices:
- Structure: Use clear hierarchical headings (H1, H2, H3)
- Clarity: Write in simple, direct language
- Examples: Include practical code examples
- Completeness: Cover installation, usage, and troubleshooting
- Maintenance: Keep documentation up-to-date with code changes
Templates
README Template
- Project overview
- Installation instructions
- Quick start guide
- API reference
- Contributing guidelines
- License information
API Documentation
- Endpoint descriptions
- Request/response examples
- Error codes
- Authentication details
Best Practices
- Use consistent formatting
- Include table of contents for long documents
- Add diagrams where helpful
- Test all code examples
- Consider your audience's technical level
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.
- 8d ago First seen · 45 lines · 11 tokens per session scan A 92ec8ed3a614
docs-writer is a skill published in the GitHub repository KylinMountain/nano-claw (4 stars, last pushed 6mo ago), licensed MIT. It adds 11 tokens to every session and 235 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
design-review-cycle
Run evidence-backed design, specification, and implementation-plan reviews through the local llm-cli-gateway stdio MCP server. Use for single-provider or complete cross-LLM design review before implementation. Covers all seven CLI request surfaces and Mistral Vibe's current accept-edits default.
model-routing
Select and dispatch llm-cli-gateway providers by live capability, target access, and task requirements. Use when choosing among Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor, or when selecting an explicit model through the local stdio gateway.
multi-llm-orchestration
Orchestrate the complete llm-cli-gateway provider surface through its local stdio MCP server. Use for parallel implementation, review, session, async-job, cache-aware prompt, and cross-LLM workflows across Claude, Codex, Gemini, Grok, Mistral, Devin, and Cursor.
agent-codex-gate
Pattern for spawning subagents whose work must receive an evidence-backed, unconditional Codex review through the local llm-cli-gateway stdio MCP server. Use when parallel implementation tasks need an independent Codex quality gate.
vibe-testing
This skill should be used when the user asks to "test my specs", "validate my design docs", "find gaps in my architecture", "stress-test the spec", "vibe test", "pressure test the docs", or mentions spec validation before implementation begins.
agnostic-model-connector
Build, debug, and optimize The Agent API / Universal SDK apps. Apps built with this skill should include prompt caching. Also handles migrating existing The Agent API code between The Agent model versions. TRIGGER when: code imports google-generativeai/@google/generative-ai; user asks for the The Agent API, Universal…