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/jayrha/agentskills/technical-writernpx skills add JayRHa/AgentSkills --skill technical-writergit clone --depth 1 https://github.com/JayRHa/AgentSkillsWrote 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/jayrha/agentskills/technical-writer)<a href="https://agentmods.dev/skills/jayrha/agentskills/technical-writer"><img src="https://agentmods.dev/badge/skills/jayrha/agentskills/technical-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 | $0.00105 | $0.01700 |
| Opus 5 | $0.00053 | $0.00850 |
| Sonnet 5 | $0.00021 | $0.00340 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
technical-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 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
Overview
Keywords: technical documentation, docs, README, how-to guide, tutorial, reference, API docs, onboarding, release notes, plain language, audience analysis, information architecture, style guide, editing, clarity.
This skill turns raw knowledge — code, features, processes, half-written notes — into documentation a real reader can act on. Good technical writing is not "explain everything"; it is "help this specific reader accomplish this specific task with the least friction." That means choosing the correct document type, ordering information so the reader is never blocked, writing in plain language, and proving claims with concrete, copy-pasteable examples.
Use the bundled resources:
references/doc-types.md— the four Diátaxis document types (tutorial, how-to, reference, explanation), when to use each, and structural templates.references/style-guide.md— plain-language rules, sentence/word patterns, formatting conventions, accessibility, and an editing checklist.scripts/readability.py— a stdlib-only readability and writing-smell analyzer (grade level, passive voice, long sentences, weasel words). Runs on any.mdor.txt.templates/how-to-guide.md— a fill-in template for a task-oriented guide.examples/before-after.md— a worked rewrite of a weak doc section into a strong one.
Workflow
Follow these steps in order. Do not start writing prose until steps 1–3 are done.
-
Identify the reader and their job. Ask or infer: Who reads this? (end user, integrating developer, ops engineer, new teammate, executive.) What is their current knowledge level? What single task or question brings them here? What do they need to be true when they leave? Write this down in one sentence: "This doc helps [reader] [accomplish task] so that [outcome]."
-
Choose the document type. Use
references/doc-types.mdand the decision table below. Mixing types in one document is the most common cause of confusing docs — keep a tutorial out of your reference, keep explanation out of your how-to.
What ships with it
5 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.
- yesterday First seen · 92 lines · 105 tokens per session scan A 1f2839cd7393
technical-writer is a skill published in the GitHub repository JayRHa/AgentSkills (4 stars, last pushed 1mo ago), licensed MIT. It adds 105 tokens to every session and 1,700 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-09-03.
Other skills, from other repositories
reverse-engineering-tools
Guide for reverse engineering protected games and anti-cheat components across user mode, kernel mode, and hypervisor-aware environments. Use this skill when analyzing drivers, IOCTL protocols, callback registration, injected-code artifacts, integrity checks, protected binaries, or debugging security-sensitive game…
design-director
Используй только внутри активного Codex Project Autopilot-проекта, когда уже выбрана проектная фаза и нужен design direction по плану автопилота.
backend-builder
Используй только внутри активного Codex Project Autopilot-проекта по утверждённому плану; не включай для обычных backend-задач вне автопилота.
project-plan
Turn a product goal or feature request into a clear Agiflow project plan with small, testable tasks in Planning status. Use when starting a project, decomposing a feature, clarifying requirements, or converting an idea into an actionable backlog.
getting-started
Assess an authenticated Agiflow workspace and recommend the right next project-management workflow. Use when a user is new to Agiflow, asks what to do next, needs orientation, or is unsure whether to plan, refine, groom, triage, or review daily status.
openclaw-debugger
Trigger when an OpenClaw agent is broken, silent, crashing, stuck, not responding, returning empty output, or the user says "my agent is down", "agent not working", "/openclaw-debugger". Walks through the standard OpenClaw 2026.4 diagnosis checklist and prints a report.