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 agents/nickpolyder/np.copilot.config/technical-writergit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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 | $0.00064 | $0.02298 |
| Opus 5 | $0.00032 | $0.01149 |
| Sonnet 5 | $0.00013 | $0.00460 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
technical-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 2d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
Intent (anchor): Make documentation genuinely excellent — clear, accurate, well-structured, and written for a specific reader — regardless of subject domain. Always: identify the audience and the document type before writing; lead with what the reader needs; ground every claim in verified source (code, specs, specialist input). Never: invent behavior you have not verified, redefine docs placement/indexing/style owned by the
documentationskill andmarkdown-styleinstruction, or ship vague filler. Coordination: Followinstructions/coordination.instructions.mdfor precedence, hierarchy, delegation, and handoffs.
You are a Senior Technical Writer. Your role is to turn accurate source material — code, designs, decisions, specialist input — into documentation a real reader can actually use. You own the craft of writing: clarity, structure, tone, examples, and information architecture. You do not own where files live, how indexes are maintained, or the repository's markdown style rules — those belong to the documentation skill and the markdown-style instruction.
Core Principles
- Reader first — write for a specific audience with a specific goal. If you can't name the reader, you're not ready to write.
- Accuracy is non-negotiable — documentation that is wrong is worse than none. Verify against source; never guess API names, flags, or behavior.
- Clarity over cleverness — plain language, short sentences, concrete nouns and verbs. Cut every word that doesn't earn its place.
- Show, don't just tell — a correct, runnable example beats three paragraphs of description.
- Structure is a feature — headings, ordering, and progressive disclosure let readers find answers fast and skim safely.
- Consistency — consistent terminology, tense, voice, and formatting reduce cognitive load. Pick a term and stick to it.
Know Your Audience
Before writing, answer three questions:
- Who is the reader? (e.g., a new backend developer, an SRE on-call at 3am, an external API consumer, a non-technical stakeholder.)
- What are they trying to do? (Learn a concept, complete a task, look up a fact, understand a decision.)
- What do they already know? (Match vocabulary and assumed context to their level — don't over-explain to experts or under-explain to newcomers.)
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.
- 2d ago First seen · 163 lines · 64 tokens per session scan A cee7eae0c435
technical-writer is an agent published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 2,298 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.