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 skills add r13v/pi-feature-dev --skill deslopgit clone --depth 1 https://github.com/r13v/pi-feature-devWrote 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/r13v/pi-feature-dev/deslop)<a href="https://agentmods.dev/skills/r13v/pi-feature-dev/deslop"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/deslop/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/skills/r13v/pi-feature-dev/deslop"><img src="https://agentmods.dev/badge/skills/r13v/pi-feature-dev/deslop.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.00035 | $0.03430 |
| Opus 5.5 | $0.00014 | $0.01372 |
| Sonnet 5.5 | $0.00007 | $0.00686 |
| Haiku 4.5 | $0.00003 | $0.00343 |
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 today.
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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deslop
Deslop removes complexity accumulated during repeated coding-agent implementation and correction cycles. It is a semantic cleanup policy, not a beautifier, dead-code sweeper, generic refactoring tool, or redesign assistant.
Priority order
Work in this order. Do not let an easy dead-code deletion displace a higher-priority cluster. The order sets what to inspect first, not what to skip: every run that has comments in scope also does the comment pass, even when a higher cluster found work.
- Test-suite bloat. Treat tests as production code that can accumulate after every agent correction. Remove duplicate, self-referential, implementation-detail, and obsolete tests while retaining a minimum sufficient set of independent behavioral evidence.
- Verification theater. Investigate checksums, receipts, manifests, validators, recomputation, and result envelopes whose producer and verifier share the same information and failure domain.
- Defensive and fallback bloat. Investigate broad catches, catch-and-fallback paths, speculative compatibility branches, repeated validation, and recovery machinery that masks errors without a current contract.
- Comment noise. Check every comment in scope. Keep only comments that explain something the code cannot show, state them about the current code rather than its history, and make each kept comment short but complete. Follow the comment check in code-smells.md.
Generic dead code, wrappers, abstractions, and ordinary duplication are secondary. Touch them only when they belong to one of the four target clusters or have direct high-confidence evidence.
Reduce test surface, not behavior surface. Evidence that a test is redundant or accumulated test-suite bloat justifies deleting or consolidating that test; it is not independent evidence for changing the production behavior the test exercises. When test-suite bloat is the active target, keep distinct externally observable production semantics—including public success, rejection, error, edge-case, and supported compatibility behavior—outside the deletion target unless the production construct is separately justified for removal by another target cluster, or direct evidence from current requirements, real callers, specifications, or history establishes that the behavior is obsolete or incorrect. Do not reclassify tested behavior as defensive or validation bloat merely because deleting its test leaves nothing else requiring it; the test may be its clearest executable specification.
What ships with it
7 files 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.
- today Changed · +7 lines affc488c8995
- 9d ago Changed · +177 lines 319e51a27fb8
- 18d ago Changed 18eb3818a45c
- 1mo ago Changed · +5 lines · +2 tokens per session d47a66d8d8da
- 1mo ago Changed · -16 tokens per session bb0e2b0c378d
- 1mo ago First seen · 127 lines · 49 tokens per session scan A 3c0d4a317916
deslop is a skill published in the GitHub repository r13v/pi-feature-dev (3 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 3,430 once invoked, about $0.0001 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-09-09.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
observability-langsmith
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
reenable-test
Guide for investigating, fixing, verifying via TDD, and re-enabling disabled or flaky Chromium tests (C++, Android Java, or WebUI). Use this skill when asked to deflake, fix, or re-enable a disabled or flaky test case, or to verify post-submit stability of a re-enabled test. Don't use for disabling a failing test…
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.