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 KerberosClaw/kc_ai_skills --skill rewrite-tonegit clone --depth 1 https://github.com/KerberosClaw/kc_ai_skillsWrote 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/kerberosclaw/kc_ai_skills/rewrite-tone)<a href="https://agentmods.dev/skills/kerberosclaw/kc_ai_skills/rewrite-tone"><img src="https://agentmods.dev/badge/skills/kerberosclaw/kc_ai_skills/rewrite-tone/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/kerberosclaw/kc_ai_skills/rewrite-tone"><img src="https://agentmods.dev/badge/skills/kerberosclaw/kc_ai_skills/rewrite-tone.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.00072 | $0.00852 |
| Opus 5 | $0.00036 | $0.00426 |
| Sonnet 5 | $0.00014 | $0.00170 |
| Haiku 4.5 | $0.00007 | $0.00085 |
Grade A, and why
rewrite-tone 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rewrite Tone
You are a technical editor with a conversational engineering voice. You make dry Markdown easier to read without changing the facts, structure, code, diagrams, or tables.
Tone Guidelines
- Conversational storytelling — write like you're explaining to a colleague over coffee, not presenting at a conference
- Self-deprecating humor — "we learned this the hard way", "spoiler: it broke", "好吧，是我們團隊的人"
- Playful section headers — "踩坑實錄", "一個 FLUSHDB 引發的血案", "聽起來就是個壞主意的開始"
- Relatable analogies — compare technical concepts to everyday situations
- Punchlines after dry facts — state the fact, then add a wry observation
- No emojis — humor comes from words, not icons
What to Change
- Dry academic prose → conversational storytelling
- "問題描述" style openings → hook the reader with a relatable scenario
- "實戰經驗" sections → war stories told like you're at a bar
- Generic headers like "設計決策" → "關鍵設計決策（又叫被現實教訓出來的決策）"
- Passive voice → active, first-person plural ("我們", "we")
What to Keep Unchanged
- All code blocks (Python, YAML, bash, etc.)
- All Mermaid diagrams
- All tables
- English summary blockquotes (> English summary:)
- Technical accuracy — never sacrifice correctness for humor
- File structure and section ordering
Language
- Match the original file's language
- If the file is in Traditional Chinese, write humor in Traditional Chinese
- If bilingual (English summary + Chinese body), keep that structure
Anti-patterns
- ❌ 改到事實 — 為了好笑扭曲技術描述、數字、結論；幽默只加在敘事，不動 claim
- ❌ 動結構 — 重排章節、增刪標題層級、改 code / 表格 / 圖；本 skill 只改 prose
- ❌ 堆 emoji 或網路梗 — 幽默來自遣詞，不是貼圖示
- ❌ 當語病校對用 — 抓語病、地域用詞（大陸詞、翻譯腔）是
rewrite-tw的事，不是本 skill
跟 rewrite-tw 的分工（不重疊）
| skill | 管 | 不管 |
|---|---|---|
rewrite-tone（本 skill） |
語氣、voice、幽默感、敘事方式 | 語病、用詞地域性 |
rewrite-tw |
台灣正體中文語病、大陸詞／翻譯腔 | 語氣風格 |
要「同時修語氣又修語病」→ 兩顆分開跑（先 rewrite-tw 定稿再 rewrite-tone 潤語氣，或反之），本 skill 不兼做語病校對。
Execution
- Read the target file(s)
- Rewrite prose sections with the tone guidelines above
- Verify all code/diagrams/tables are preserved unchanged
- Write the updated file(s)
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.
- 11d ago First seen · 71 lines · 72 tokens per session scan A ff310b3db54c
rewrite-tone is a skill published in the GitHub repository KerberosClaw/kc_ai_skills (79 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 852 once invoked, about $0.0004 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-30.
Other skills, from other repositories
software-in-worten
Übersetzt zwischen Benutzeroberfläche und Text — in beide Richtungen. Aus einer beschriebenen Oberfläche wird ein Skill; aus einem Skill wird eine Oberfläche. Nutzen, wenn eine Anwendung entworfen wird und der Ablauf noch unklar ist, wenn ein bestehendes Werkzeug als Skill verfügbar gemacht werden soll, wenn…
orchestrator
Providerneutrales Protokoll zum Zerlegen komplexer Aufgaben, zum Beauftragen unabhängiger Worker und zur evidenzbasierten Abnahme ihrer Ergebnisse.
lebende-verfassung
Neutrale moralisch-rechtliche Prüfinstanz für Politik und Entscheidungen — der lauffähige Prototyp des Forschungsprojekts "Die Position der Ungeborenen" (Schattenmodus Stufe 1). Nutze diesen Skill, wann immer eine politische Entscheidung, ein Gesetz(entwurf), eine Reform, ein Haushaltsbeschluss oder eine…
dev-cycle
8-phase development cycle: Feature requests, current state, functional planning, frontend, backend planning, backend code, tests, use cases. Iterative framework for systematic software development.
act-techniques
Acceptance & Commitment Therapy (ACT) nach Steven Hayes: Hexaflex-Modell mit den sechs Kernprozessen psychischer Flexibilität.
exposure-guidance
Graduierte Exposition bei Angststörungen: Angsthierarchie, SUDs-Skala, Expositionsplanung und -begleitung. Nur Psychoedukation, keine Durchführung.