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/rikdc/ai-skills/cleangit clone --depth 1 https://github.com/rikdc/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/commands/rikdc/ai-skills/clean)<a href="https://agentmods.dev/commands/rikdc/ai-skills/clean"><img src="https://agentmods.dev/badge/commands/rikdc/ai-skills/clean.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.00007 | $0.00204 |
| Opus 5 | $0.00003 | $0.00102 |
| Sonnet 5 | $0.00001 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
Grade A, and why
clean 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 5d 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
-
Look for comments that are obvious or redundant and remove them. Examples of
comments that can be removed include:
- Commented out code.
- Comments that describe edits like "added", "removed", or "changed" something.
- Explanations that are just obvious because they are close to method names.
-
Do not delete all comments:
-
Don't remove comments that indicate code is a stub for future work.
-
Don't remove comments that start with TODO.
-
Don't remove comments if doing so would make a scope empty, like an empty catch
block or an empty else block.
-
Don't remove comments that suppress linters or formatters, like
// prettier-ignore
-
-
If you find any end-of-line comments, move them above the code they describe.
Comments should go on their own lines.
Look at the local code changes that are not yet committed to git
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.
- 5d ago First seen · 30 lines · 7 tokens per session scan A 83fb2367821c
clean is a command published in the GitHub repository rikdc/ai-skills (2 stars, last pushed today), licensed MPL-2.0. It adds 7 tokens to every session and 204 once invoked, about $0.0000 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
learn
Force claude-smart to extract learnings from this session now.
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.