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/lootlog/monorepo/technical-writingnpx skills add lootlog/monorepo --skill technical-writinggit clone --depth 1 https://github.com/lootlog/monorepoWrote 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/lootlog/monorepo/technical-writing)<a href="https://agentmods.dev/skills/lootlog/monorepo/technical-writing"><img src="https://agentmods.dev/badge/skills/lootlog/monorepo/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.1 | $0.00043 | $0.00263 |
| Opus 5 | $0.00022 | $0.00131 |
| Sonnet 5 | $0.00009 | $0.00053 |
| Haiku 4.5 | $0.00004 | $0.00026 |
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 5d 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
Write for a tired engineer who needs the point quickly.
Pick the document mode
- Tutorial: teach by producing visible results.
- How-to: give steps toward a concrete goal.
- Reference: state complete facts for lookup.
- Explanation: explain bounded context, rationale, and trade-offs.
Do not mix modes when separate linked documents would be clearer.
Write
- Use the repository's real symbols, paths, flags, commands, and domain terms.
- Put conditions before actions. Write instructions as commands.
- Prefer active voice, plain words, and one main thought per sentence.
- Cut filler, vague attribution, promotional language, and claims without evidence.
- Use numbered lists for sequences and bullets for unordered items.
- Keep headings in sentence case.
- State expected output or observable success for procedural steps.
- Write PR titles, PR descriptions, and Changeset summaries in English.
- Follow Conventional Commits for commit messages.
Apply the unslop skill as the final editing pass. Preserve required legal, API, and domain terminology.
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.
- 5d ago First seen · 32 lines · 43 tokens per session scan A ec86d5ece2ff
technical-writing is a skill published in the GitHub repository lootlog/monorepo (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 263 once invoked, about $0.0002 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
plan-update
Use when you need to update a plan document with deep research across all compiler passes. Launches parallel subagents to analyze how a topic affects every compiler phase, then consolidates findings into the plan doc.
skill-locations
Document Remotion skill placement. Use when adding, moving, or editing Remotion skills to decide whether a skill belongs in .agents/skills as an internal skill or packages/skills as a public skill.
adversarial-document-reviewer
Conditional document-review persona, selected when the document has >5 requirements or implementation units, makes significant architectural decisions, covers high-stakes domains, or proposes new abstractions. Challenges premises, surfaces unstated assumptions, and stress-tests decisions rather than evaluating…
video-transcripts
Generate structured video transcripts from local files or video URLs using Gemini Files API. Use when a GitHub or Linear tracker item, comment, or attachment includes a screen recording, .mov, .mp4, or tracker-hosted video and you need a block instead of hand-written notes.
changeset
Changesets document package changes for release. Concise bullets, imperative voice, user impact only.
widget-authoring
Author or edit ThinkEx widgets, which are self-contained interactive HTML blocks inside documents. Use when the user explicitly asks for a widget, asks for interaction or live computation, or wants a document visual that ordinary blocks cannot express.