technical-writing

technical-writing is a skill for Claude Code from saffron-health/libretto. It costs 43 tokens per session (204 once invoked), scanned A, original, MIT.

A set of guidelines for writing technical documentation, specifications, README files, and agent instructions. It focuses on concise, complete sentences and clear structure.

In plain words
What is it for?
Use it when creating or editing specifications, documentation, READMEs, AGENTS.md files, or other Markdown content.
Why use it?
It helps readers understand technical information without repeated explanations or unnecessary formatting. It also encourages consistent references to files and external resources.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/name/project/docs/testing.md.

Part of the libretto plugin — 24 skills shipped together

Good fit Use it when creating or editing specifications, documentation, READMEs, AGENTS.md files, or other Markdown content.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add saffron-health/libretto
Claude Code
/plugin install libretto

Made for: Claude Code.

Or install libretto, the plugin that ships this one along with the rest of its 24 skills.

Wrote 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.

agentmods badge for technical-writing

README.md
[![agentmods](https://agentmods.dev/badge/skills/saffron-health/libretto/technical-writing/github.svg)](https://agentmods.dev/skills/saffron-health/libretto/technical-writing)
Your own site
<a href="https://agentmods.dev/skills/saffron-health/libretto/technical-writing"><img src="https://agentmods.dev/badge/skills/saffron-health/libretto/technical-writing/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.

agentmods 80×15 button for technical-writing

Your own site · 80×15
<a href="https://agentmods.dev/skills/saffron-health/libretto/technical-writing"><img src="https://agentmods.dev/badge/skills/saffron-health/libretto/technical-writing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.00204
Opus 5 $0.00022 $0.00102
Sonnet 5 $0.00009 $0.00041
Haiku 4.5 $0.00004 $0.00020

Measured 9d ago against content hash d37834a0eeea, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

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 9d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/technical-writing/SKILL.md · 31 lines

What it actually says

Technical Writing

Audience

Assume readers are at least as smart as you, so do not over-explain. State information once and move on.

Style

Write concise, complete sentences using active voice and present tense. Each paragraph or bullet should express a single idea.

Formatting

  • Do not use emojis.
  • Do not use bold or italics.
  • Use headings, lists, and code blocks only when they add clarity.
  • Use fenced code blocks with language identifiers.

Paths

Always use relative file paths: docs/testing.md, not /Users/name/project/docs/testing.md.

Do Not Repeat

Link to existing resources instead of duplicating content. Reference other docs, web pages, or files rather than restating their information.

Changes

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.

  1. 9d ago First seen · 31 lines · 43 tokens per session scan A d37834a0eeea

Subscribe to this mod's changes

technical-writing is a skill published in the GitHub repository saffron-health/libretto (889 stars, last pushed 19d ago), licensed MIT. It adds 43 tokens to every session and 204 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-30.