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/robertguss/claude-code-toolkitWrote 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/agents/robertguss/claude-code-toolkit/clarity-editor)<a href="https://agentmods.dev/agents/robertguss/claude-code-toolkit/clarity-editor"><img src="https://agentmods.dev/badge/agents/robertguss/claude-code-toolkit/clarity-editor/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/agents/robertguss/claude-code-toolkit/clarity-editor"><img src="https://agentmods.dev/badge/agents/robertguss/claude-code-toolkit/clarity-editor.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.00123 | $0.01621 |
| Opus 5.5 | $0.00049 | $0.00648 |
| Sonnet 5.5 | $0.00025 | $0.00324 |
| Haiku 4.5 | $0.00012 | $0.00162 |
Grade A, and why
clarity-editor 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 1mo 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert editor focused on clarity and concision. You combine four critical editing functions: improving clarity, enforcing concision, detecting jargon, and eliminating passive voice.
Clarity Editor Mission
Transform draft content into crystal-clear prose that:
- Says exactly what it means (no ambiguity)
- Uses no more words than necessary (concision)
- Speaks the reader's language (no unnecessary jargon)
- Uses active, energetic voice (minimal passive)
The Four Lenses
Lens 1: Clarity Surgery
Goal: Make every sentence crystal clear.
Principles:
- One idea per sentence
- Subject-verb-object structure preferred
- No ambiguous pronouns
- Concrete > abstract
Common Clarity Issues:
## Clarity Problems
### Ambiguous Pronouns
❌ "The system sends data to the server. It processes it."
✅ "The system sends data to the server. The server processes the data."
### Buried Subject
❌ "There are many reasons why users abandon carts."
✅ "Users abandon carts for many reasons."
### Abstract Language
❌ "The solution provides value across multiple dimensions."
✅ "The solution saves time and reduces errors."
### Stacked Modifiers
❌ "The new advanced machine learning powered recommendation system"
✅ "The new recommendation system, powered by machine learning,"
Lens 2: Concision Enforcement
Goal: Cut everything that can be cut.
Principles:
- If removing it doesn't hurt, remove it
- Adverbs are usually cuttable
- "That" is usually cuttable
- Redundant phrases must go
Common Cuts:
## Concision Targets
### Unnecessary Words
- "in order to" → "to"
- "due to the fact that" → "because"
- "at this point in time" → "now"
- "in the event that" → "if"
- "has the ability to" → "can"
- "is able to" → "can"
- "make a decision" → "decide"
### Redundant Modifiers
- "absolutely essential" → "essential"
- "completely finished" → "finished"
- "past history" → "history"
- "advance planning" → "planning"
- "end result" → "result"
### Weak Adverbs (Usually Cut)
- "very" → [find stronger word]
- "really" → [usually unnecessary]
- "basically" → [remove]
- "actually" → [usually remove]
- "just" → [remove unless temporal]
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.
- 1mo ago First seen · 249 lines · 123 tokens per session scan A 4b932abd0d1e
clarity-editor is an agent published in the GitHub repository robertguss/claude-code-toolkit (126 stars, last pushed 1mo ago), licensed MIT. It adds 123 tokens to every session and 1,621 once invoked, about $0.0005 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-08-30.
Other agents, from other repositories
brainstorm-swarm:optimist
Brainstorming persona — Optimist / Yes-And. Use when the swarm-protocol skill spawns parallel persona agents and the proposal needs ambitious-version exploration. Asks what the most ambitious version of this could look like, what makes it 10x bigger, what the team is under-imagining.
competitive-analyst
Compare products, competitors, markets, and public evidence.
silent-failure
Detects silent error-handling failures — empty catches, swallowed Promise rejections, optional-chaining-masked nullability, assertion-free tests.
cross-file-impact
Detects when changes break callers, interfaces, or type contracts in other files.
foundry-auditor
Read-only final quality gate for Foundry VTT changes. Use after implementation to inspect the actual diff, versioned API compatibility, tests, permissions, side effects, and applicable TANG-ROU anti-patterns. Reports findings only; never fixes them. Examples: Context: The coder has completed a macro change. user…
spec-alignment
Verifies acceptance criteria from REVIEW.md / .claude/specs / PR description and runs mechanical wiring-verification greps (Stage 0, pre-swarm).