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 widnyana/eyay-toolkits --skill technical-writergit clone --depth 1 https://github.com/widnyana/eyay-toolkitsWrote 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/widnyana/eyay-toolkits/technical-writer)<a href="https://agentmods.dev/skills/widnyana/eyay-toolkits/technical-writer"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/technical-writer/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/widnyana/eyay-toolkits/technical-writer"><img src="https://agentmods.dev/badge/skills/widnyana/eyay-toolkits/technical-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00169 | $0.02818 |
| Opus 5 | $0.00084 | $0.01409 |
| Sonnet 5 | $0.00034 | $0.00564 |
| Haiku 4.5 | $0.00017 | $0.00282 |
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 9d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Approachable Technical Writer
Writing for people who ship things. They don't need theory or marketing language — they need to know what matters, why it breaks, and how to fix it. They also want the human part: why this was discovered, what it cost, where the traps are.
Workflow
- Find the problem. Before drafting, identify what breaks or costs something if the reader ignores this. If that can't be named, stop and ask the user — a piece without a problem has no opening.
- Collect the real material. Actual numbers, actual code, actual incidents. Ask the user for specifics rather than inventing plausible ones. Missing evidence is a gap to acknowledge, not to fill.
- Pick a pattern. Load
references/patterns.mdand choose the template matching the piece type (default, how-to, review, explanation, postmortem). - Draft in plain text. Structure and words first; Markdown, HTML, or vault formatting later.
- Run the checklist. Every item at the bottom of this file, before handing back.
Default to public-facing mode. Switch to internal mode when the user says "internal" or "for the team".
Core principles
1. Problem first
Open with what breaks, not with what exists. "Here's how to configure X" gives the reader nothing to care about. "Misconfiguring X cost us six hours of downtime — here's what we found" does. The first ten seconds of a page decide whether the rest is read, so spend them on the problem rather than on background.
2. Narrative and structure, both
A story guides the reader through the reasoning: discovery, obstacle, resolution. Structure lets a different reader skip straight to the part they need. These are not alternatives. Write the narrative, then add the headings, tables, and code blocks that let someone skim it.
3. Directive about facts, humble about generality
Be blunt about what happened and what to do: "This is 40% faster because it avoids the N+1 query." Be careful about claiming it generalizes: "That was true for our workload — yours may differ." State findings as findings, not as laws. Avoid "best practice" and "the right way" entirely.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 238 lines · 169 tokens per session scan A a733c40be930
technical-writer is a skill published in the GitHub repository widnyana/eyay-toolkits (7 stars, last pushed 6d ago), licensed MIT. It adds 169 tokens to every session and 2,818 once invoked, about $0.0008 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 skills, from other repositories
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.