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 New1Direction/korgex --skill writing-clearlygit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/writing-clearly)<a href="https://agentmods.dev/skills/new1direction/korgex/writing-clearly"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/writing-clearly.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.1 | $0.00019 | $0.00268 |
| Opus 5 | $0.00010 | $0.00134 |
| Sonnet 5 | $0.00004 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
Grade A, and why
writing-clearly 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.
What it actually says
Clear writing is a faithful, compressed model of the truth. Cut anything that doesn't change the reader's understanding.
General
- Lead with the point. Say what changed / what to do, then the why. No preamble.
- Be concrete and specific over vague and grand. Prefer plain words to jargon.
- Don't overstate: state verified facts plainly; flag the uncertain as uncertain.
Code comments 4. Comment the WHY, not the WHAT — well-named identifiers already say what. Add a comment only when the reason is non-obvious. Match the file's existing density.
Docs & messages 5. Match length to the reader's need: a commit subject is one line; a function doc is its contract (purpose, params, returns, failure); a status update is a sentence or two — what changed, what's next. 6. Show, don't tell: a short example beats a paragraph of description.
Red flags: marketing adjectives, restating code in English, walls of text where a list or example would do, hedging on things you've verified.
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 · 28 lines · 19 tokens per session scan A 604f9302fc8f
writing-clearly is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 19 tokens to every session and 268 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-08-31.
Other skills, from other repositories
telegram
Owner-only Telegram text bridge and Mini App gateway for the existing Ouroboros interface.
omp
Bounded Oh My Pi (omp) provider shortcut via Elves. Use when the user says /omp or "use omp" for a one-shot task.
setup-cobbler
Configure Cobbler model routes and external-agent preferences for this checkout. Use when the user types /setup-cobbler, asks to set up Cobbler model routes, onboard models, or update which tools handle planning/implement/review in Claude Code.
claudexor
Use the local Claudexor control plane for harness-agnostic coding work across Claude Code, Codex, Cursor, and OpenCode. Use when a task benefits from route-aware harness and account selection, quota-aware account rotation, shared thread context, read-only planning or research, best-of-N execution, or cross-harness…
fugu
Run a bounded Sakana Fugu repository task or explicit review through codex-fugu. Use when the user types /fugu, asks to use Fugu, or asks for a Fugu review.
elves-grok-bot
Unattended-run kernel for Grok Bot non-git work. Use when the user says "use elves" for a long unattended job with no PR/merge model.