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 OutlineDriven/outline-driven-development --skill deslopgit clone --depth 1 https://github.com/OutlineDriven/outline-driven-developmentWrote 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/outlinedriven/outline-driven-development/deslop)<a href="https://agentmods.dev/skills/outlinedriven/outline-driven-development/deslop"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/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/outlinedriven/outline-driven-development/deslop"><img src="https://agentmods.dev/badge/skills/outlinedriven/outline-driven-development/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.00049 | $0.04794 |
| Opus 5 | $0.00024 | $0.02397 |
| Sonnet 5 | $0.00010 | $0.00959 |
| Haiku 4.5 | $0.00005 | $0.00479 |
Grade B, and why
deslop scanned grade B with 1 finding 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
1. **HIGH deterministic scan.** Use `search` for line patterns and `ast-grep` where syntax shape matters. Record `{file, line, pattern, certainty: HIGH, strategy}` for each finding. Categories: debug output (stream-writi How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deslop
Four modes share one spine: bound scope, verify with the repo's own command, rollback on regression, atomic commits separate from behavior changes.
Contract
| Field | Bound contract |
|---|---|
| Trigger | The user says deslop, debloat, tidy, simplify, clean up this diff, deslop a branch diff, remove dead code, find placeholders or stubs, remove dead fields, redundant wrappers, or stale config, or the slop skill routes code findings here |
| Authority | Reversible local: writes only production source files or prose artifacts (may run the repo verifier and git restore on regression); rollback is version control or undo. No remote mutation. |
| Side effect | Local writes to production source files or prose artifacts; no edits to tests, fixtures, mocks, examples, generated, vendored, or lockfile/build artifacts |
| Done | Mode-specific done predicate holds; verifier green or rollback confirmed |
Refusal
Not for behavior changes, new abstractions, or refactors that introduce patterns: a tidy pass that would change observable behavior stops and reports a candidate for a separate refactor. Not for remote, credential, publish, deploy, or irreversible changes. Not for duplication across artifacts or drift: those are handed off, not force-compressed. Not for non-code targets (memory, git workspace, docs): route to their owners. Not for opportunistic sweeps across untouched files in tidy mode: the candidate must lie in code already under edit.
Mode selection
| User says | Mode | Target |
|---|---|---|
| deslop, remove debug code, find placeholders or stubs, remove dead code, slop routed here | slop | Production source files |
| debloat, tighten this, too long | bloat | One padded prose artifact (document, skill, spec) |
| tidy this up, simplify, clean up this diff, polish my changes, make this simpler | tidy | Code in the working tree |
| dead field, redundant wrapper, stale config, duplicate state, speculative abstraction | tidy | Code already under edit |
| deslop this branch diff, remove AI debris from my branch, clean up added lines only | diff | Added/modified lines in a branch diff |
What ships with it
5 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.
- 2d ago Changed · -25 tokens per session 39a4353377e1
- 5d ago First seen · 142 lines · 74 tokens per session scan B d04bdd04fdc0
deslop is a skill published in the GitHub repository OutlineDriven/outline-driven-development (52 stars, last pushed 3d ago), licensed Apache-2.0. It adds 49 tokens to every session and 4,794 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
audit-project
Run an iterative multi-agent code audit until critical and high findings are resolved. Use when the user says "audit my code", "find all the bugs", "deep code audit", "iterative review", or "review until clean".
optimize
Use when asked to optimize code, speed up a path, reduce allocations, repair a regression, or profile a target. Not for remote, credential, publish, deploy, or irreversible changes.
debug
Hypothesis-driven debugging. Use when a test fails, a crash or exception occurs, output is wrong, or an intermittent flake has no obvious cause.
ios-build-fix
Use when asked to run /ios-build-fix to fix a failing iOS build, regenerate an Xcode project from project.yml, or correct UI behavior. Not for a clean rebuild: use ios-build-cleanup.
strike-the-root
Use when a bug, failure, flake, regression, review finding, or ticket needs the core fixed so it cannot recur. Not for greenfield features: use tdd. Not for style-only review or typo-class one-liners.
extremely-optimize
Use when asked to run a performance campaign against a measured floor. Not for hypothesis-only analysis without mutation: use fastopt.