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 jpoehnelt/skills --skill comms-technical-writinggit clone --depth 1 https://github.com/jpoehnelt/skillsWrote 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/jpoehnelt/skills/comms-technical-writing)<a href="https://agentmods.dev/skills/jpoehnelt/skills/comms-technical-writing"><img src="https://agentmods.dev/badge/skills/jpoehnelt/skills/comms-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.
<a href="https://agentmods.dev/skills/jpoehnelt/skills/comms-technical-writing"><img src="https://agentmods.dev/badge/skills/jpoehnelt/skills/comms-technical-writing.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.00050 | $0.01121 |
| Opus 5.5 | $0.00020 | $0.00448 |
| Sonnet 5.5 | $0.00010 | $0.00224 |
| Haiku 4.5 | $0.00005 | $0.00112 |
Grade A, and why
comms-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 8d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical writing
Write so a tired engineer understands on the first read. Apply all layers.
Repo facts: where the repo keeps durable docs, design records, and change notes or changesets, and any style guides for user-facing copy (AGENTS.md or CLAUDE.md).
Three rules sit above them:
- Cut every word that does no work. "In order to" is "to".
- Use the short, everyday word. "Use", not "utilize". A long word must buy its length with precision.
- When a rule makes a sentence worse, fix the sentence another way. A sentence that obeys every rule and sounds machine-written has failed.
The codebase is the word list. Write the real symbol, file, flag, or command name. Do not invent jargon. Use words a developer says out loud: "move", "delete", "a budget that only decreases". Preserve the author's meaning and uncertainty when editing.
Vary the rhythm
- Mix sentence lengths. Short sentences land a point. Longer ones carry a fact with its condition.
- Have a view where the mode allows it. Explanation weighs trade-offs. Reference stays dry.
- Be specific. Not "schema changes can cause issues" but "a column rename fails the build".
Pick one mode per document
Ask whether the content serves action or understanding, and learning or work.
- Tutorial (action, learning). Say what the learner will build. Every step shows a visible result and the expected output. Explanation is one clause and a link.
- How-to (action, work). Solve a task the reader already has. Assume competence. Action only, no background. Name the guide by the task.
- Reference (understanding, work). Describe only. No instruction or opinion. Dry, complete, mirrors the structure of the thing described.
- Explanation (understanding, learning). One bounded topic. Give context, constraints, alternatives. Opinion is allowed here only.
Do not mix modes. Split and link instead.
Sentences
- Address the reader as "you", in the present tense.
- Name the actor: "the compiler checks", not "is checked".
- Write instructions as commands. Put the condition first: "To delete the file, run X."
- Put the common case first and exceptions after.
- No "please", "simply", "easy", or "quickly" in a procedure.
- Link with words that say where the link goes. Never "click here".
- Headings carry the point, in sentence case. One h1 per page, no skipped levels.
- Numbered lists for sequences, bullets otherwise. Introduce lists with a full sentence. Keep items parallel.
- Code in code font. Use serial commas. Drop "etc.".
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.
- 8d ago Changed · -1 lines ed18a7d59026
- 9d ago First seen · 83 lines · 50 tokens per session scan A 4c058f97b1be
comms-technical-writing is a skill published in the GitHub repository jpoehnelt/skills (23 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 1,121 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-10-21.
Other skills, from other repositories
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.