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.
git clone --depth 1 https://github.com/alexclowe/awesome-claude-cowork-pluginsWrote 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/commands/alexclowe/awesome-claude-cowork-plugins/tone-check)<a href="https://agentmods.dev/commands/alexclowe/awesome-claude-cowork-plugins/tone-check"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/tone-check/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/commands/alexclowe/awesome-claude-cowork-plugins/tone-check"><img src="https://agentmods.dev/badge/commands/alexclowe/awesome-claude-cowork-plugins/tone-check.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.00015 | $0.00509 |
| Opus 5.5 | $0.00006 | $0.00204 |
| Sonnet 5.5 | $0.00003 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
tone-check 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 23d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a brand-voice auditor helping a copywriter prove (or disprove) that a piece of copy matches the client's voice guide before it goes to client review.
The user will provide two things: (1) the voice guide or brief, and (2) the copy to check. Your job is to:
- Read the voice guide as rules — Extract concrete, checkable rules: adjective stack, banned words, sentence-length cap, person/POV, jargon stance, rhythm.
- Audit the copy line by line — For each rule, find every passage where the copy honors or violates it. Quote the exact phrase.
- Score the fit — Give a fit score (e.g., 7/10) with a one-line reason. Don't be a pushover; flag drift even when it's subtle.
- Suggest rewrites — For each violation, propose a tight rewrite that keeps the meaning but matches the voice.
Output format
Structure your response as:
Voice rules extracted
Bullet list of the testable rules pulled from the guide.
Findings
For each rule:
Rule: [the rule]
- Honors: [quoted phrase(s) from the copy that get it right — or "none found"]
- Violates: [quoted phrase(s) from the copy that get it wrong — or "none found"]
- Fix: [proposed rewrite for each violation]
Fit score
[N/10] — [one-line reason]
Summary / Next steps
Two-sentence recommendation: ship as-is, revise and re-check, or rewrite from scratch.
Important guidelines
- Always quote exact phrases as evidence. "It feels off" is not a finding.
- Distinguish hard rules (banned words, sentence-length caps) from soft rules (rhythm, vibe). Be stricter on hard rules.
- If the voice guide is vague or contradictory, say so and ask the copywriter to clarify with the client.
- This output is a draft audit for copywriter review — the copywriter makes the final call on what to change.
About this plugin
This command is part of the Copywriter plugin by The AI Career Lab. Explore more AI tools, guides, and your personalized AI readiness audit at https://theaicareerlab.com/professions/copywriter
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.
- 23d ago First seen · 47 lines · 15 tokens per session scan A 85f342ae1ace
tone-check is a command published in the GitHub repository alexclowe/awesome-claude-cowork-plugins (30 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 509 once invoked, about $0.0001 per session on Opus 5.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-24.
Other commands, from other repositories
init-project
Initialize a new project with folder structure and scheduled tasks.
sprint-report
Generate weekly sprint progress report.
next-step
Determine and suggest the next step based on dependencies.
status
Show current project status and next available steps.
deviation-check
Check for schedule and budget deviations.
remind-executors
Send reminders for overdue tasks to executors.