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 spinningrachel/career-engine --skill technical-writinggit 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/skills/spinningrachel/career-engine/technical-writing)<a href="https://agentmods.dev/skills/spinningrachel/career-engine/technical-writing"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/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/spinningrachel/career-engine/technical-writing"><img src="https://agentmods.dev/badge/skills/spinningrachel/career-engine/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.00057 | $0.04585 |
| Opus 5 | $0.00028 | $0.02292 |
| Sonnet 5 | $0.00011 | $0.00917 |
| Haiku 4.5 | $0.00006 | $0.00458 |
Grade A, and why
technical-writing scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = requests.get(f"{BASE_URL}/users/{user_id}") How it starts
The opening of the file, as written. The whole thing — 436 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writing — Analysis Procedures
career-datadata root (R-37). When producing output for the user's own professional context — portfolio docs, bio text, personal brand copy, or career materials — load${CAREER_DATA}/references/01-writing-rules.mdfor voice preferences and attribution rules, and${CAREER_DATA}/references/03-framework.md→ §Voice fingerprint for tone alignment. These files govern personal register; this skill governs document structure, clarity, and engineering style. For general technical documentation, the career-data files are optional. If${CAREER_DATA}was not provided (standalone invocation), locate thecareer-dataskill yourself, confirmcareer-data-marker.json, and apply the orchestrator's healthy / damaged / absent outcomes before reading.
Working Approach
These behavioral rules govern every task — writing, editing, reviewing, and advising:
- Read existing content before suggesting changes. Match established patterns.
- Push back on ideas when doing so leads to better documentation. State the reason.
- Start with the smallest reasonable changes. Do not restructure what does not need restructuring.
- Never add content that serves the wrong audience for the guide being edited.
- When uncertain about a convention, check 2–3 existing sections of the document for precedent.
Core Principles
- Second person, active voice, confident delivery. Address the reader as "you." State what the system does and what the reader does. Never use passive voice where active works.
- Vary sentence length deliberately. Very long sentences for complex relationships with multiple dependent clauses. Long sentences for procedures connecting related steps. Short sentences for emphasis and critical warnings. Never produce monotonous rhythm.
- 12th-grade reading level. Precision over simplicity; brevity over exhaustiveness.
- Full sentences with real connectors doing the work. No artificial rhythm from fragmented prose broken into bullets. Reserve bullets for true lists.
- Trust the reader. State points directly. Remove filler words. Never explain what the reader can infer.
- No pleasantries. Never: "please", "kindly", "feel free to", "you may want to."
- No hedging. Never: "may", "might", "could potentially", "it is possible that." State capabilities as facts.
- No marketing language. Never: "revolutionize", "seamlessly", "leverage", "powerful", "best-in-class", "cutting-edge." State what the system does.
- Professional, not formal. Write like a capable colleague explaining a system — not a manual author performing expertise.
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 First seen · 436 lines · 57 tokens per session scan A ed73d63c46d6
technical-writing is a skill published in the GitHub repository spinningrachel/career-engine (4 stars, last pushed 27d ago), licensed MIT. It adds 57 tokens to every session and 4,585 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…