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/i9wa4/dotfiles/technical-writingnpx skills add i9wa4/dotfiles --skill technical-writinggit clone --depth 1 https://github.com/i9wa4/dotfilesWrote 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/i9wa4/dotfiles/technical-writing)<a href="https://agentmods.dev/skills/i9wa4/dotfiles/technical-writing"><img src="https://agentmods.dev/badge/skills/i9wa4/dotfiles/technical-writing.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.00079 | $0.00500 |
| Opus 5 | $0.00039 | $0.00250 |
| Sonnet 5 | $0.00016 | $0.00100 |
| Haiku 4.5 | $0.00008 | $0.00050 |
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 4d 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
Technical Writing
Owns meaning-preserving editing, translation, terminology, rhythm, and QA.
1. Workflow
- Identify surface: English, Japanese, translation, skill text, or QA.
- Preserve meaning. Do not rewrite commands, identifiers, product names, paths, code, links, versions, or APIs for style.
- Keep glossary/terminology polish here when meanings are stable; use
clarify-conceptsfirst when they are not. - For generic/AI-like prose, read Prose Review.
- For English checks, read Vale And Harper.
- For English-to-Japanese, clean English first, then read English-to-Japanese Workflow and Japanese Writing Style.
- For Japanese editorial review, read Japanese Writing Style.
- For flat explanatory prose, read Cognitive Rhythm. Build rhythm from source material.
- Apply only clarity changes; preserve facts and intent.
2. Boundaries
Issue 225/226 boundaries: no automation, model/cost/privacy, external-sharing approval, derivative publication approval, or chunking.
Do not add direct polished-Japanese drafting from scratch. Repair English first, then translate or QA Japanese.
3. References
What ships with it
10 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.
- evals/eval.yaml 526 B
- evals/tasks/negative-trigger-1.yaml 426 B
- evals/tasks/positive-trigger-1.yaml 454 B
- evals/tasks/positive-trigger-2.yaml 434 B
- references/cognitive-rhythm.md 6.0 KB
- references/english-to-japanese-technical-translation.md 17 KB
- references/english-to-japanese-workflow.md 17 KB
- references/japanese-writing-style.md 8.3 KB
- references/prose-review.md 3.5 KB
- references/vale-and-harper.md 4.4 KB
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.
- 4d ago First seen · 55 lines · 79 tokens per session scan A d4a095eac930
technical-writing is a skill published in the GitHub repository i9wa4/dotfiles (11 stars, last pushed today), licensed MIT. It adds 79 tokens to every session and 500 once invoked, about $0.0004 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-30.
Other skills, from other repositories
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.
po-translate
Orchestrate English→Japanese translation of po/ja.po — classify, delegate translation/review to subagents, iterate until clean.
gui-debug
Verify a rendering or window-chrome change in any macOS GUI app unattended — find its CGWindowID via JXA, capture that window alone (with per-pixel alpha) using screencapture -l, and read exact RGBA via NSBitmapImageRep. Use for blur/opacity/corner-radius/glyph/color rendering bugs where a screenshot or pixel value is…
bootstrap-prd
Set up PRD-driven development infrastructure for a new project, including directory structure, templates, and roadmap.
taskgo
Maintains a private Git-backed personal project and task control repository using concise current Markdown, derived Git history, ADRs, and status synchronization. Use when tracking tasks, updating project status (STATUS.md), managing ADRs, synchronizing tracker state, delegating tasks to external agents, or generating…
audit
Eight audit modes (codebase — owns "audit the codebase" — docs/process, performance, threat-model, motion, SEO, debt). Triggers "nuclear review", "whole codebase review", "adversarial audit", "fable audit", "correctness audit", "audit the docs", "doc drift", "process audit", "perf audit", "why is it slow", "bundle…