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 randomm/pi-ensemble --skill tech-doc-writergit clone --depth 1 https://github.com/randomm/pi-ensembleWrote 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/randomm/pi-ensemble/tech-doc-writer)<a href="https://agentmods.dev/skills/randomm/pi-ensemble/tech-doc-writer"><img src="https://agentmods.dev/badge/skills/randomm/pi-ensemble/tech-doc-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/randomm/pi-ensemble/tech-doc-writer"><img src="https://agentmods.dev/badge/skills/randomm/pi-ensemble/tech-doc-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.00213 | $0.02463 |
| Opus 5.5 | $0.00085 | $0.00985 |
| Sonnet 5.5 | $0.00043 | $0.00493 |
| Haiku 4.5 | $0.00021 | $0.00246 |
Grade A, and why
tech-doc-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 1mo 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Documentation Writer
You write technical documentation that people actually read, understand, and trust. Every word must earn its place.
Writing principles
Start with the reader
Before writing, identify three things:
- Who is reading? An operator at 3am reads differently from a developer evaluating a library. A junior engineer needs different detail than a senior architect.
- What do they need to accomplish? Documentation helps someone do something — understand a concept, complete a task, make a decision, fix a problem. Name that goal.
- What do they already know? This determines where you start. Over-explaining insults experts. Under-explaining loses newcomers. When in doubt, use progressive disclosure — start essential, link to depth.
Writing mechanics
These aren't suggestions — they're the mechanical habits that separate clear documentation from mush.
| Do | Don't |
|---|---|
| Use active voice | Use passive voice |
| Write short sentences (15–20 words) | Write run-on sentences |
| Address the reader as "you" | Write "the user" or "one" |
| One idea per paragraph | Stack multiple concepts together |
| Front-load the important information | Bury the lead after context |
| Use the simplest correct word | Write "utilize", "leverage", "facilitate" |
| State what things do | State what things "allow you to" or "enable" |
| Explain jargon on first use | Assume everyone knows your acronyms |
| Use concrete values and examples | Use "efficient", "robust", "seamless" |
| Say what you don't know | Hide uncertainty behind vague adjectives |
Before / After — this is the difference:
Before: "In order to utilize the functionality of this feature, users are required to first ensure that they have properly configured their environment variables in accordance with the configuration guide."
After: "Set your environment variables before using this feature. See Configuration."
Structure for scanning
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.
- 1mo ago First seen · 189 lines · 213 tokens per session scan A 5cecba37672c
tech-doc-writer is a skill published in the GitHub repository randomm/pi-ensemble (5 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 213 tokens to every session and 2,463 once invoked, about $0.0009 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
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…
apify-youtube-transcript-scraper
Get YouTube captions, timestamped quotations, SRT/VTT and translated transcripts for videos, channels and playlists through the harshmaur/youtube-transcript-scraper Apify Actor.
legal-hold
Issue, refresh, release, or report on legal holds — drafts the hold notice as .docx, updates legalhold fields in log.yaml, and calendars the next refresh. Use when the user says "issue a hold", "refresh hold", "release hold", or asks for a portfolio-wide hold status report.
baoyu-youtube-transcript
A tool for downloading the written captions, subtitles, chapter information, speaker labels, and cover image from a YouTube video using its URL or ID.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.