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 EthanYoQ/Skill-hub --skill yq-technical-writinggit clone --depth 1 https://github.com/EthanYoQ/Skill-hubWrote 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/ethanyoq/skill-hub/yq-technical-writing)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/yq-technical-writing"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/yq-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/ethanyoq/skill-hub/yq-technical-writing"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/yq-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.00028 | $0.01712 |
| Opus 5 | $0.00014 | $0.00856 |
| Sonnet 5 | $0.00006 | $0.00342 |
| Haiku 4.5 | $0.00003 | $0.00171 |
Grade A, and why
yq-technical-writing 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 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.
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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Prose Standard
Write enough to preserve the contract, then remove reasoning transcripts, repetition, and decoration. A contract is an obligation, invariant, precondition, postcondition, compatibility promise, failure behavior, timing rule, or ownership rule that a caller, callee, implementer, producer, consumer, operator, or user relies on.
This skill owns sentence-level editorial judgment and required prose coverage. Use yq-doc-maintenance for placement, source-of-truth ownership, stale/conflicting documents, and corpus structure. Use yq-remove-reasoning-leaks when prose adopts the authoring session's vantage. This is guidance, not a mechanical shortening pass.
Terms such as contract, boundary, shape, surface, seam, gate, and vocabulary are useful only when they name the exact subject. Prefer the concrete API, field set, invariant, validation, timing point, component split, or failure state when that is clearer.
Comments describe non-obvious contracts or rationale that code cannot express. Let code show ordinary control flow.
Scope, authority, and ownership
Use the narrowest scope supported by the request, current change, or named artifact. Ask only when ambiguity could cause a broad or destructive rewrite. Do not infer repository-wide scope from a request about one file or diff.
Accept mode: automatic | interactive; default to automatic. Interactive mode is for explicit calibration or questions, not permission. Audit and review tasks report findings without editing. Explicit write, fix, rewrite, or trim tasks may apply clear changes inside the authorized scope.
Read applicable agent instructions, documentation rules, style guides, owning code/config/schema, and current decision records before judging prose. Discover project-specific exclusions and derivative surfaces. Third-party sources, recorded fixtures, snapshots, and frozen archives are immutable by default. Generated surfaces must be updated through their owner and regenerated. Treat translations according to the repository's localization and pairing policy; either language may be the authored owner.
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.
- 8d ago First seen · 83 lines · 28 tokens per session scan A a819286c50c7
yq-technical-writing is a skill published in the GitHub repository EthanYoQ/Skill-hub (9 stars, last pushed 6d ago), licensed MIT. It adds 28 tokens to every session and 1,712 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
gws-sheets
Google Sheets: Read and write spreadsheets.
hive.pdf
Read, write, merge, split, rotate, watermark, encrypt, and OCR PDF files using Python (pypdf, pdfplumber, reportlab, pypdfium2) and command-line tools (poppler-utils, qpdf). Use when the user asks to extract text/tables/images from a PDF, create or modify a PDF, combine or split PDFs, OCR a scanned PDF…
gws-docs
Read and write Google Docs.
gws-forms
Read and write Google Forms.
recipe-email-drive-link
Share a Google Drive file and email the link with a message to recipients.
recipe-share-event-materials
Share Google Drive files with all attendees of a Google Calendar event.