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 dork-labs/dorkos --skill writing-for-humansgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/writing-for-humans)<a href="https://agentmods.dev/skills/dork-labs/dorkos/writing-for-humans"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/writing-for-humans/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/dork-labs/dorkos/writing-for-humans"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/writing-for-humans.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.00069 | $0.01498 |
| Opus 5 | $0.00034 | $0.00749 |
| Sonnet 5 | $0.00014 | $0.00300 |
| Haiku 4.5 | $0.00007 | $0.00150 |
Grade A, and why
writing-for-humans 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing for Humans
Every word a user reads should be plain enough for a smart 9th grader who does not write code. This skill is the readability standard for user-facing DorkOS writing. It is the shared source the other writing skills build on.
The readability contract
Hold every user-facing sentence to these five rules:
- Aim for a 9th-grade reading level. If a sentence needs a second read, rewrite it.
- Keep sentences short. Aim under 20 words. Never pack two big ideas into one sentence. Split them.
- Use active voice with a clear actor. Say who does what: "DorkOS opens your browser," not "the browser is opened."
- Lead with the benefit, then the mechanism (if at all). Say what the user gets first. Most of the time you can drop the mechanism.
- Define or drop every technical term. Either avoid the jargon or gloss it in the same sentence. Prefer numbers and concrete scenarios over abstractions.
House punctuation rule: no em dashes. They invite run-on sentences that smuggle in a second idea; use a comma, colon, parentheses, or a new sentence instead.
What this governs (and what it does not)
Governs every surface a user reads: changelog fragments, release notes, READMEs, npm package copy, the GitHub repo description, docs/ guide and concept pages, blog posts, UI microcopy, and error messages.
Does not govern surfaces written for developers or coding agents, which stay precise and technical:
- ADRs →
writing-adrs contributing/developer guides and API reference pages →writing-developer-guides- Code comments → keep them technical (
.claude/rules/conventions.md)
When a page mixes both (a user guide with a developer-reference tail), split it with a clear heading like ## Reference and a framing sentence so the reader knows the audience just shifted.
Brand voice note: meta/brand-foundation.md §10 has two registers. This skill is the plain-language register. Brand vocabulary (Autonomous, Orchestration, Operator) is allowed here only with an in-sentence gloss.
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 Changed · +69 tokens per session 5f96f2cd6c7e
- 12d ago First seen · 100 lines · 0 tokens per session scan A 66453ed5a5c1
writing-for-humans is a skill published in the GitHub repository dork-labs/dorkos (9 stars, last pushed today), licensed MIT. It adds 69 tokens to every session and 1,498 once invoked, about $0.0003 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
hive.slack-notifications-setup
Set up a Slack notification channel (Sentinel) for a colony by driving the browser — reuse or create the "Hive Sentinel" Slack app from a JSON manifest, install it, capture the bot + app tokens, create/select the channel via the Slack API, and turn Sentinel on so the colony can ping the user on Slack and accept…
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…
hive.note-taking
Maintain a free-form scratchpad of decisions, extracted values, and open questions so context pruning doesn't lose anything you still need.
sdlc-accelerate
End-to-end SDLC ramp-up from idea to construction-ready with automated phase transitions.
ralph-memory
Manage Al semantic memory entries — list, query, and clear lessons learned across loop iterations.
project-awareness
Detect project type, AIWG framework state, team configuration, and active work to summarize status and recommend next actions.