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 skills/mh4gf/claude-code/deslopnpx skills add MH4GF/claude-code --skill deslopgit clone --depth 1 https://github.com/MH4GF/claude-codeWrote 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/mh4gf/claude-code/deslop)<a href="https://agentmods.dev/skills/mh4gf/claude-code/deslop"><img src="https://agentmods.dev/badge/skills/mh4gf/claude-code/deslop.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.00085 | $0.00489 |
| Opus 5 | $0.00043 | $0.00244 |
| Sonnet 5 | $0.00017 | $0.00098 |
| Haiku 4.5 | $0.00009 | $0.00049 |
Grade A, and why
deslop 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 4d 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
Deslop
origin/main との diff を読み、AI 生成コードに紛れがちなパターンを検出して指摘する。ファイル編集は行わない。修正判断は呼び出し元に委ねる。
検出対象
- 周辺コードのスタイルと一致しない不要なコメント
- 信頼できる内部パスでの過剰な try/catch・防御チェック
- 型エラー回避だけが目的の
anyキャスト - 早期リターンで平坦化できる深いネスト
- ファイル全体の慣習と乖離した書き方
手順
- ベースブランチを判定する（既定:
origin/main、無ければorigin/master） git diff <base>...HEADで変更内容を取得する- 検出対象に該当する箇所をファイルパス・行番号付きでリスト化する
- 各指摘に「なぜノイズか」と「推奨書き換え」を 1〜2 行で添える
出力フォーマット
## Deslop 指摘
- <path>:<line> — <カテゴリ> — <推奨書き換え>
...
## サマリ
<1〜3 文。検出ゼロなら「該当なし」とだけ書く>
ガードレール
- 振る舞いが変わる可能性のある指摘は明示的にフラグを立てる
- 大規模な書き換え提案は出さない。最小・局所修正のみ
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.
- 4d ago First seen · 41 lines · 85 tokens per session scan A 6ae5c4009658
deslop is a skill published in the GitHub repository MH4GF/claude-code (2 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 489 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…