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 vincentkoc/dotskills --skill technical-deslopgit clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/technical-deslop)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/technical-deslop"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/technical-deslop.svg" alt="Measured on agentmods" 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.00021 | $0.00314 |
| Opus 5 | $0.00010 | $0.00157 |
| Sonnet 5 | $0.00004 | $0.00063 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
technical-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 8d 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
Technical Deslop
Purpose
Clean branch/staged diffs by removing AI-style slop and restoring repo-consistent style without changing behavior.
When to use
- A diff feels over-explained, overly defensive, or inconsistent with surrounding code.
- You need a final cleanup pass before review/PR.
- You want to normalize style after automated generation.
Workflow
- Capture scope with
git diff --cachedandgit diff $(git merge-base origin/main HEAD)..HEAD. - Focus only on changed hunks (or user-scoped files).
- Apply the cleanup sequence in
references/playbook.md. - Remove slop patterns: redundant comments, unnecessary defensive branches, non-idiomatic casts, and style drift.
- Re-check behavior boundaries: no logic changes unless the user explicitly requested them.
- Report a short 1-3 sentence summary of cleanup performed.
Read references/slop-patterns.md for detection rules and references/playbook.md for execution order.
Inputs
- Optional file scope (
FILES) or explicit user file targets. - Current branch diff and staged diff.
- Repository conventions from local instructions/config.
Outputs
- Behavior-preserving cleanup in touched files.
- Minimal summary of what was normalized and where.
What ships with it
4 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.
- 8d ago First seen · 42 lines · 21 tokens per session scan A 8229dd1ce319
technical-deslop is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 314 once invoked, about $0.0001 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
taiyi-review
A pre-merge review guide for checking code changes, design decisions, tests, and documentation. A merge adds reviewed changes to the main code branch.
verify-implementation
A workflow that runs a project’s verification skills to produce a report on coding patterns, architecture rules, and project conventions. It is intended for work after implementation, before a pull request, or during code review.
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., .tsx, .ts, .js). Support both pending-change reviews and focused file reviews while applying the checklist rules.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
repo-conventions
NeuroLink's review standards — the critical rules to enforce, what NOT to comment on, the security bar, hot paths. Load before reviewing any change in this repository.