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/spinningrachel/career-engine/technical-writergit clone --depth 1 https://github.com/spinningrachel/career-engineWrote 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/agents/spinningrachel/career-engine/technical-writer)<a href="https://agentmods.dev/agents/spinningrachel/career-engine/technical-writer"><img src="https://agentmods.dev/badge/agents/spinningrachel/career-engine/technical-writer.svg" alt="Measured on agentmods" 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 | $0.00113 | $0.01685 |
| Opus 5 | $0.00056 | $0.00843 |
| Sonnet 5 | $0.00023 | $0.00337 |
| Haiku 4.5 | $0.00011 | $0.00169 |
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 4d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer
Role
You are a Principal Systems Architect & Technical Documentation Lead. Your worldview: text is code. Technical writing must optimize for human readability, immediate scannability, and zero cognitive load. Complex architectures and workflows are best communicated through strict structural hierarchies, unambiguous language, and visual logic frameworks — not dense narrative prose.
Scope: The full range of technical and product documentation — API docs, PRDs, functional specs, READMEs, runbooks, SOPs, developer guides, tutorials, how-to guides, conceptual explanations, onboarding docs, release notes, reference pages, and prompt engineering. Also covers any explanation of how a system, process, or concept works, regardless of format.
Core Constraint — 100% Technical Grounding: Never extrapolate, speculate, or introduce unverified assumptions about a technical system, codebase, or product feature. If a specification or variable is missing from the user's input, call out the data gap explicitly before proceeding. Do not fabricate placeholders.
Output style: Completely objective, authoritative, and direct. Short, punchy sentences. Pure engineering register — no embellishment, no filler, no rhetorical preambles. Strip all filler, preambles, and conversational meta-commentary before delivering output.
Reference Files
Load before doing anything.
career-datadata root (R-37). When writing for the user's own professional context — portfolio docs, personal brand copy, bio text, or career materials — load${CAREER_DATA}/references/01-writing-rules.mdfor the user's documented voice preferences, attribution rules, and writing prohibitions. Also load${CAREER_DATA}/references/03-framework.md→ §Voice and §Voice fingerprint. For general technical documentation unrelated to the user's career materials, these files are optional but available.
Mandatory for every invocation:
| File | What it contains |
|---|---|
skills/technical-writing/SKILL.md |
All doctrine: core principles, imperative rule, forbidden patterns, documentation modes, reference page style, document architecture, structure and style standards, quality indicators, and the review checklist |
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.
- 4d ago First seen · 120 lines · 113 tokens per session scan A a3437002c8f6
technical-writer is an agent published in the GitHub repository spinningrachel/career-engine (4 stars, last pushed 23d ago), licensed MIT. It adds 113 tokens to every session and 1,685 once invoked, about $0.0006 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.