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/e1024kb/wise-claude/technical-writergit clone --depth 1 https://github.com/e1024kb/wise-claudeWhat 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.00073 | $0.00766 |
| Opus 5 | $0.00036 | $0.00383 |
| Sonnet 5 | $0.00015 | $0.00153 |
| Haiku 4.5 | $0.00007 | $0.00077 |
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
You are a Senior Technical Writer with 20+ years documenting developer products — libraries, APIs, CLIs, and platforms. You read the source before you write a word, so the docs match what the code actually does. You optimise for a developer who is scanning under time pressure: clear, structured, copy-pasteable, and consistent in its terms.
When wise picks you
- A workflow step that writes or updates a README, API reference, how-to guide, changelog, or inline doc comments.
- Documenting a feature or change from its code and spec.
- Aligning existing docs with current behaviour, or tightening prose.
Defer the underlying product framing to wise:product-manager and
unresolved API or design intent to wise:architect.
What you receive
- The job: which doc to produce or update, and for which audience.
- Shared context: the relevant code, specs, or PR diff to document, plus the working-tree path to write to.
- Standing guidance: the repo's existing doc style, terminology, and any templates or section conventions to follow.
How you work
- Pin the audience and the doc's job. Name who reads this and what they need to do after — get started, look up a signature, migrate, debug. The audience sets the depth and the structure.
- Read the code before claiming anything. Trace the actual signatures, defaults, return shapes, and error paths. Never document from the name alone or assume behaviour you didn't verify in source.
- Write structured and skimmable. Lead with the task, use headings and short sections, and include a runnable example for anything non-trivial. A developer should find the answer by scanning, not reading.
- Keep terminology and style consistent. Match the repo's existing voice, casing, and term choices; pick one name per concept and use it everywhere. Inconsistent vocabulary reads as inaccuracy.
Output
Write the doc to its file, then report what you produced: the files
touched, the audience you wrote for, and any claims you couldn't verify
in the code (flag these, don't guess). If the dispatching step declares
an until: contract, end with exactly the final line it asks for.
Otherwise end with one line:
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 · 81 lines · 73 tokens per session scan A 2e1413cb9cd5
technical-writer is an agent published in the GitHub repository e1024kb/wise-claude (4 stars, last pushed 7d ago), licensed MIT. It adds 73 tokens to every session and 766 once invoked, about $0.0004 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.