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 agentmods add commands/eugeniughelbur/clearmode/clear-explaingit clone --depth 1 https://github.com/eugeniughelbur/clearmodeWrote 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/eugeniughelbur/clearmode/clear-explain)<a href="https://agentmods.dev/commands/eugeniughelbur/clearmode/clear-explain"><img src="https://agentmods.dev/badge/commands/eugeniughelbur/clearmode/clear-explain.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 | $0.00037 | $0.00220 |
| Opus 5 | $0.00018 | $0.00110 |
| Sonnet 5 | $0.00007 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
clear-explain 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 3d 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-explain
Explain a rule, or defend it.
Steps
- Run
python3 scripts/clearcheck.py --explain <RULE_ID>. Never paraphrase a rule from memory. - Give the reason first, then the fix, then the before-and-after.
- If the user thinks the rule is wrong on their line, decide honestly:
- The rule is right: show the fix on their exact sentence.
- The rule is wrong here: tell them to suppress it inline with
clear: ignore <RULE_ID>. - The rule is wrong in general: edit
rules/clear-100.json, then runpython3 scripts/compile_targets.py. The rule pack is the argument, not the chat.
- With no rule id, list the axes and the error-severity rules, nothing more.
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.
- 3d ago First seen · 19 lines · 0 tokens per session scan A 3b2f21228555
clear-explain is a command published in the GitHub repository eugeniughelbur/clearmode (1 stars, last pushed 5d ago), licensed MIT. It adds 37 tokens to every session and 220 once invoked, about $0.0002 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 commands, from other repositories
deslop
Audit and rewrite text so it stops reading as AI-generated.
build-carousel
Produce a LinkedIn carousel SPEC (slide copy + visual brief + image-gen prompts) for assembly in Canva or Figma.
find-ideas
Interview the user to surface specific, postable LinkedIn ideas from their actual work.
repurpose-content
Turn one piece of source content into 3-7 distinct LinkedIn pieces from different angles.
rewrite-profile
Rewrite the full LinkedIn profile as one coherent positioning unit.
write-post
Draft a LinkedIn text post in the user's voice with inline humanizer drafting constraints.