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 henryh/AI-SpecDoc --skill technical-writergit clone --depth 1 https://github.com/henryh/AI-SpecDocWrote 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/henryh/ai-specdoc/technical-writer)<a href="https://agentmods.dev/skills/henryh/ai-specdoc/technical-writer"><img src="https://agentmods.dev/badge/skills/henryh/ai-specdoc/technical-writer/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/henryh/ai-specdoc/technical-writer"><img src="https://agentmods.dev/badge/skills/henryh/ai-specdoc/technical-writer.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.00061 | $0.00675 |
| Opus 5.5 | $0.00024 | $0.00270 |
| Sonnet 5.5 | $0.00012 | $0.00135 |
| Haiku 4.5 | $0.00006 | $0.00068 |
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 2mo 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
Overview
Update project documentation as part of task completion and capture decisions in ADRs when the project requires ADRs and process, testing, or development approaches change.
Workflow
- Identify doc targets via docs/index.md.
- Summarize task outcomes and update the relevant docs with concise, testable statements.
- If a decision was made or a workflow/testing approach changed, add a dated ADR entry in docs/adr.md only when the project requires ADRs.
- Verify task statuses: ensure no leftovers, duplicates, or stale fragments between
ActiveandDone; correct any inconsistencies found. - If review raised questions or uncovered gaps, note them in the relevant doc (or ADR) and align on next steps.
- Keep updates minimal and consistent with existing tone and structure.
Mandatory Documentation Triggers
- If the user explicitly requests documentation changes during a task, treat them as required for TW: apply the doc updates as part of the documentation phase before closing the task.
ADR Guidance
- Add ADRs only if the project requires ADRs.
- If ADRs are required, add them for: decisions made during implementation or review, changes to testing strategy, or development workflow updates.
- Keep ADRs concise: context, decision, consequences, date.
- One ADR entry must capture exactly one decision. If there are multiple decisions, split them into separate ADR entries.
- Append new ADR entries to docs/adr.md; do not overwrite prior decisions.
Output Checklist
- Docs updated only where scope changed.
- ADR added when decisions or workflow/testing changes occurred and the project requires ADRs.
- Task lists checked for clean statuses (no duplicates or leftovers between
ActiveandDone). - Review questions captured and reconciled with documentation.
Output Discipline
- Find first, then read the minimum necessary.
- Do not read large files unless required.
- Avoid large quotes; return a concise extract instead of raw text.
- Output should be a compressed container, not a dialogue.
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.
- 2mo ago First seen · 56 lines · 61 tokens per session scan A 6ad941aeb549
technical-writer is a skill published in the GitHub repository henryh/AI-SpecDoc (2 stars, last pushed 8mo ago), licensed MIT. It adds 61 tokens to every session and 675 once invoked, about $0.0002 per session on Opus 5.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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…