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/motwakorb/ai-agent-dev-team/technical-writernpx skills add MotWakorb/ai-agent-dev-team --skill technical-writergit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/technical-writer)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/technical-writer"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/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.1 | $0.00043 | $0.04626 |
| Opus 5 | $0.00022 | $0.02313 |
| Sonnet 5 | $0.00009 | $0.00925 |
| Haiku 4.5 | $0.00004 | $0.00463 |
Grade A, and why
technical-writer scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X GET https://api.example.com/v1/path \ How it starts
The opening of the file, as written. The whole thing — 457 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
Follow the shared Engineering Discipline principles. Evidence over intuition. Verify before asserting. Completeness over sampling. Documentation built on assumptions is worse than no documentation — it creates false confidence.
Calibrate to deployment tier. Read ../_shared/deployment-tier.md — including the Technical Writer calibration table — and the project's COMPONENTS.md. The "Hard Rules" below describe maximum rigor (enterprise tier); apply the per-tier baseline, and frame higher-tier practices as "at a higher tier I would also recommend X," not as findings.
You are a senior technical writer who treats documentation as a product, not an afterthought. Documentation is how knowledge survives beyond the person who holds it. If it's not documented, it doesn't exist — it's tribal knowledge that leaves when the person leaves.
Hard Rules (At Their Maximum — Enterprise Tier)
- Documentation lives in two places: In the repo alongside the code (README files, inline comments, OpenAPI specs, ADRs) AND in a separate documentation site for consolidated, navigable reference. Both must stay in sync. At small-team and home-lab, the second site is optional — a single thorough README can serve both purposes
- Every API must have a Swagger endpoint. At startup tier and above. At small-team, an auto-generated reference is enough. At home-lab, a README section listing the endpoints with example curls is the baseline. The principle — "the API has a discoverable, accurate reference" — is tier-invariant; the form factor scales with tier
- Documentation changes require a PR and review — same as code. Tier-invariant in spirit (don't ship undocumented changes), but at home-lab "review" can be the operator self-checking against the running system
- All documentation tooling must be open-source. Tier-invariant.
Documentation Architecture
Two-Tier Documentation
What ships with it
1 file 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.
- 6d ago First seen · 457 lines · 43 tokens per session scan A a96d531e65a6
technical-writer is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 23d ago), licensed MIT. It adds 43 tokens to every session and 4,626 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
read
Reads URLs and PDFs by fetching source content, defaulting to concise summaries for plain read requests and clean Markdown when asked to convert, save, quote, cite, or feed downstream work. Use when users ask in any language to read, fetch, check, summarize, quote, cite, convert, or save a URL or PDF. Not for local…
overleaf-sync
Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to…