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/codewithmukesh/dotnet-claude-kit/de-sloppifynpx skills add codewithmukesh/dotnet-claude-kit --skill de-sloppifygit clone --depth 1 https://github.com/codewithmukesh/dotnet-claude-kitWrote 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/codewithmukesh/dotnet-claude-kit/de-sloppify)<a href="https://agentmods.dev/skills/codewithmukesh/dotnet-claude-kit/de-sloppify"><img src="https://agentmods.dev/badge/skills/codewithmukesh/dotnet-claude-kit/de-sloppify.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.00115 | $0.01376 |
| Opus 5 | $0.00057 | $0.00688 |
| Sonnet 5 | $0.00023 | $0.00275 |
| Haiku 4.5 | $0.00012 | $0.00138 |
Grade A, and why
de-sloppify 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/de-sloppify — 7-Step Cleanup Pipeline
What
Runs an ordered, verified cleanup pipeline over a .NET codebase. Order matters: formatting first (it touches every file — get the churn out of the way before anything else), dead code late (earlier steps reveal it). Random cleanup misses things and creates merge conflicts; the pipeline doesn't.
Three rules make it safe:
- Verify after each step —
dotnet build+dotnet testbetween steps. A cleanup that breaks something is worse than the mess it was fixing. - Commit per step — each step is its own commit, so a bad Step 4 reverts without losing Steps 1-3.
- Safe removals only — before deleting "dead" code, check for reflection, DI-convention, and serialization usage that Roslyn cannot see.
Per-step commands, safety checklists, and code examples live in
references/cleanup-steps.md — read it before executing.
When
- "Clean up", "tidy up", "de-sloppify", "housekeeping", "tech debt"
- After a large feature merge or dependency upgrade (new warnings accumulate)
- Pre-release hardening, or a scheduled quarterly cleanup sprint
- Before performance work (dead code out, classes sealed for devirtualization)
- Never mixed with feature work — cleanup commits stay pure
How
Step 0: Pick the Steps
| Scenario | Steps to run |
|---|---|
| Full cleanup pass / pre-release / quarterly | All 7 |
| Quick tidy before PR | 1, 2, 6 |
| After large feature merge | 1, 2, 3, 4 |
| After dependency upgrade | 2, 3 |
| Before performance work | 4, 6 |
| CI warning threshold exceeded | 3 only |
| Tech debt sprint | 4, 5 |
Steps 1-7 (execute in order, details in references/cleanup-steps.md)
| # | Step | Tool | Commit message |
|---|---|---|---|
| 1 | Format all code | dotnet format |
chore: apply dotnet format |
| 2 | Remove unused usings | dotnet format analyzers --diagnostics IDE0005 |
chore: remove unused using statements |
| 3 | Fix analyzer warnings | MCP get_diagnostics → triage by category |
chore: fix analyzer warnings |
| 4 | Remove dead code | MCP find_dead_code + safety check (reflection/DI/serialization grep) |
chore: remove dead code |
| 5 | Resolve TODOs | grep TODO/HACK/FIXME → fix, file issue, or delete | chore: resolve TODO comments |
| 6 | Seal non-inherited classes | MCP get_type_hierarchy per candidate + test-project grep |
chore: seal non-inherited classes |
| 7 | Propagate CancellationToken | MCP detect_antipatterns → trace async chains |
chore: propagate CancellationToken through async chains |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 117 lines · 115 tokens per session scan A a22114ca95bc
de-sloppify is a skill published in the GitHub repository codewithmukesh/dotnet-claude-kit (693 stars, last pushed 28d ago), licensed MIT. It adds 115 tokens to every session and 1,376 once invoked, about $0.0006 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-30.
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…