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 DauQuangThanh/hanoi-rainbow --skill technical-writinggit clone --depth 1 https://github.com/DauQuangThanh/hanoi-rainbowWrote 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/dauquangthanh/hanoi-rainbow/technical-writing)<a href="https://agentmods.dev/skills/dauquangthanh/hanoi-rainbow/technical-writing"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/technical-writing/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/dauquangthanh/hanoi-rainbow/technical-writing"><img src="https://agentmods.dev/badge/skills/dauquangthanh/hanoi-rainbow/technical-writing.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.00106 | $0.01208 |
| Opus 5 | $0.00053 | $0.00604 |
| Sonnet 5 | $0.00021 | $0.00242 |
| Haiku 4.5 | $0.00011 | $0.00121 |
Grade A, and why
technical-writing 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 10d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writing
Creates professional technical documentation with clear structure, appropriate detail level, and user-focused content.
Workflow
1. Identify Documentation Type
Determine which type of documentation is needed:
- API Documentation - REST, GraphQL, webhooks, authentication
- User Guides - Features, how-tos, troubleshooting
- Tutorials - Learning-focused with hands-on examples
- Architecture Documents - System design, technical decisions
- README Files - Project overview, quick start
- Release Notes - Changes, migrations, breaking changes
- Technical Specifications - Requirements, constraints
For detailed templates and patterns: Load documentation-types-and-workflows.md
2. Gather Context
Collect essential information before writing:
- Audience - Developers, end-users, managers, administrators
- Technical depth - Beginner, intermediate, advanced
- Scope - Codebase/APIs/systems to document
- Standards - Style guides or organizational requirements
- Related docs - Existing documentation to reference or integrate with
3. Structure Content
Apply clear organization principles:
- Lead with overview/introduction
- Use descriptive heading hierarchy (H1 → H2 → H3)
- Include table of contents for documents with >3 sections
- Group related information logically
- Place examples immediately after concepts
- Add diagrams/visuals for complex workflows
4. Write Clear Content
Follow core writing principles:
- Active voice - "The API returns..." not "The response is returned..."
- Specificity - "Response time < 200ms" not "Fast response"
- Define acronyms - "API (Application Programming Interface)" on first use
- Consistent terminology - Same terms throughout document
- Imperative instructions - "Run the command" not "You should run..."
- Show examples - Provide code/output for every concept
For comprehensive style guidance: Load writing-guidelines.md
What ships with it
2 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.
- 10d ago First seen · 165 lines · 106 tokens per session scan A a4c35a8f31da
technical-writing is a skill published in the GitHub repository DauQuangThanh/hanoi-rainbow (16 stars, last pushed 7mo ago), licensed MIT. It adds 106 tokens to every session and 1,208 once invoked, about $0.0005 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
spec-driven-development
Spec-first workflow where an executable, testable specification is written before code and becomes the single source of truth that tests verify against, flowing spec → acceptance criteria → tasks → implementation.
ospec-change
Create or advance a lightweight OSpec change using the classic fast workflow.
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.