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 AnastasiyaW/codex-claude-code-config --skill deslopgit clone --depth 1 https://github.com/AnastasiyaW/codex-claude-code-configWrote 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/anastasiyaw/codex-claude-code-config/deslop)<a href="https://agentmods.dev/skills/anastasiyaw/codex-claude-code-config/deslop"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/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/anastasiyaw/codex-claude-code-config/deslop"><img src="https://agentmods.dev/badge/skills/anastasiyaw/codex-claude-code-config/deslop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00592 |
| Opus 5 | $0.00032 | $0.00296 |
| Sonnet 5 | $0.00013 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
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 9d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deslop
Review only the branch diff against its intended base and remove noise that does not belong in the local code style. Keep the behavior and public contract unchanged unless a clear, separately verified bug is fixed.
Review Targets
- comments that narrate obvious code or contradict local conventions;
- defensive checks or catch blocks abnormal for a trusted path;
any, unsafe casts, or optionality used only to silence a type checker;- deep nesting that can be made clearer with early returns or a named helper;
- one-off wrappers, flags, and branches inconsistent with the surrounding module;
- C++ ownership or error-handling scaffolding that is redundant with the established RAII/contract boundary.
Workflow
- Inspect the base, diff, local style, tests, and ownership boundaries.
- Classify each candidate as noise, a clear bug, or an intentional contract.
- Remove only confirmed noise in a focused edit.
- Run the narrow relevant checks and inspect the final diff.
- If the structure needs a real redesign, stop deslop and use
refactoring-safely,architecture-quality, orthermo-nuclear-code-quality-review.
Do not delete comments that explain a non-obvious invariant, security boundary, ABI constraint, workaround with an owner, or externally required behavior.
Gotchas
- Shorter code is not automatically clearer; preserve names and boundaries that carry domain meaning.
- A broad formatter run can hide behavior changes and is not deslop proof.
- Removing a defensive check without proving the trusted-path invariant can turn cleanup into a regression.
- In C++, exception and ownership code may look repetitive while protecting an ABI or lifetime boundary; inspect callers before removing it.
Troubleshooting
| Symptom | Likely cause | Action |
|---|---|---|
| Cleanup changes a test result | Candidate was behavior, not noise | Revert that candidate and isolate the real contract |
| Diff is too broad | Tool ran over the whole tree | Restrict review to the branch diff and restore unrelated files |
| Comment seems redundant but explains a constraint | Context is outside the file | Read the owning docs/tests before changing it |
| Code remains structurally tangled | Deslop is the wrong scope | Escalate to a planned refactor with characterization tests |
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.
- 9d ago First seen · 59 lines · 63 tokens per session scan A 81cdb29ed6d4
deslop is a skill published in the GitHub repository AnastasiyaW/codex-claude-code-config (149 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 592 once invoked, about $0.0003 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
discount-review
Inspect the discount policy fixture with a repeatable review checklist and helper script.
code-review
Perform comprehensive code reviews focusing on best practices, security vulnerabilities, performance optimization, and maintainability.
code-review
Reviews code for bugs, security issues, and best practices.
lfe-hygiene
Conduct a structural audit of the repository to detect "Documentation Drift" or "Spaghetti Files." Use in Phase 5 (Hygiene sub-pipeline, Step 1).
lfe-dep-audit
Inspector sub-skill. Reviews dependency manifest files (package.json, requirements.txt, go.mod, Cargo.toml, pom.xml) changed in the current diff for risky version patterns and stale majors. Emits a human-run audit instruction rather than executing tools. Writes .plans/checks/depfindings.md. Called by lfe-inspector…
lfe-security-check
Inspector sub-skill. Runs an OWASP Top-10 prompt-based security analysis on the current implementation diff. No external tooling required — pure LLM reasoning. Writes .plans/checks/securityfindings.md. Called by lfe-inspector when enabled in inspector-config.md.