Borrowing it
Nothing to install: this file belongs to randomparity/hmc-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/randomparity/hmc-mcp/main/.agents/skills/desloppify/SKILL.mdgit clone --depth 1 https://github.com/randomparity/hmc-mcpWrote 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/randomparity/hmc-mcp/desloppify)<a href="https://agentmods.dev/skills/randomparity/hmc-mcp/desloppify"><img src="https://agentmods.dev/badge/skills/randomparity/hmc-mcp/desloppify.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.1 | $0.00056 | $0.04021 |
| Opus 5 | $0.00028 | $0.02011 |
| Sonnet 5 | $0.00011 | $0.00804 |
| Haiku 4.5 | $0.00006 | $0.00402 |
Grade C, and why
desloppify scanned grade C 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 yesterday.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Clean up after: `rm -rf /tmp/desloppify-fix` How it starts
The opening of the file, as written. The whole thing — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Desloppify
1. Your Job
Maximise the strict score honestly. Your main cycle: scan → plan → execute → rescan. Follow the scan output's INSTRUCTIONS FOR AGENTS — don't substitute your own analysis.
Don't be lazy. Do large refactors and small detailed fixes with equal energy. If it takes touching 20 files, touch 20 files. If it's a one-line change, make it. No task is too big or too small — fix things properly, not minimally.
2. The Workflow
Three phases, repeated as a cycle.
Monorepos and multi-project directories
If the workspace contains multiple programs (e.g., frontend + backend in sibling folders), scan each one separately — do not scan the parent directory:
desloppify --lang typescript scan --path ./frontend
desloppify --lang python scan --path ./backend
Each --path target should be a single coherent project. Scanning a parent that contains multiple programs mixes state and path context, producing unreliable results.
Phase 1: Scan and review — understand the codebase
desloppify scan --path . # analyse the codebase
desloppify status # check scores — are we at target?
After scanning, always run desloppify next — it tells you exactly what to do, in order. Don't interpret the scan output yourself or ask the user what to do. Just run next and follow its instructions.
The scan will tell you if subjective dimensions need review. Follow its instructions. To trigger a review manually:
desloppify review --prepare # then follow your runner's review workflow
Phase 2: Plan — decide what to work on
After reviews, triage stages and plan creation appear in the execution queue surfaced by next. Complete them in order — next tells you what each stage expects in the --report:
desloppify next # shows the next execution workflow step
desloppify plan triage --stage observe --report "themes and root causes..."
desloppify plan triage --stage reflect --report "comparison against completed work..."
desloppify plan triage --stage organize --report "summary of priorities..."
desloppify plan triage --complete --strategy "execution plan..."
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.
- yesterday Changed · -11 lines 646f3c0b7e0d
- 6d ago First seen · 341 lines · 56 tokens per session scan C c481221a7b7d
desloppify is a skill published in the GitHub repository randomparity/hmc-mcp (1 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 4,021 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.