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 jscraik/Agent-Skills --skill unslopifygit clone --depth 1 https://github.com/jscraik/Agent-SkillsWrote 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/jscraik/agent-skills/unslopify)<a href="https://agentmods.dev/skills/jscraik/agent-skills/unslopify"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/unslopify/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/jscraik/agent-skills/unslopify"><img src="https://agentmods.dev/badge/skills/jscraik/agent-skills/unslopify.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.00033 | $0.01163 |
| Opus 5 | $0.00016 | $0.00581 |
| Sonnet 5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
unslopify 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unslopify Mode
Turn vague cleanup discomfort into evidence, a small cleanup ledger, and validation proof before edits happen. Start with 2-3 focused surfaces unless the user explicitly expands scope.
When To Use
- Unused or dead code.
- Stale exports, dependencies, duplicate artifacts, or placeholder scaffolding.
- Minor type, dependency, fallback, or error-handling cleanup with local evidence.
Escalate architectural redesigns, API boundary changes, migrations, and cross-surface redesigns out of this skill.
Philosophy
Make cleanup boring, scoped, reversible, and evidence-first.
Runtime Activation
$unslopify is global. Use it against the active target repo, not Agent Skills
Kit by default. Before claiming runtime skill use, confirm it was available in
the current command surface. If runtime proof, route visibility, or user links
are blocked, do not treat direct SKILL.md reading as runtime activation;
repair/sync the runtime surface or classify the work as source inspection.
Use target-repo validation for ordinary cleanup. Agent Skills Kit gates apply only when maintaining this package or its projections.
Package Maintenance Gates
Run only when editing, syncing, publishing, or claiming readiness for this package:
<agent-skills-root>/bin/ask skills resolve unslopify --json<agent-skills-root>/bin/ask skills proof unslopify --runtime-target codex --json --robot<agent-skills-root>/bin/ask skills handles --check --json- Strict skill audit for package changes.
- External review or Plugin Eval when wording, cost, shape, or evals changed.
- Workspace/user sync proof before projection or runtime-readiness claims.
Stop package maintenance if a required gate fails. Route checks prove metadata
only; they do not replace proof. Use ./bin/ask ... only in Agent Skills Kit.
Required inputs
- Target cleanup scope, diff, or file set.
- Repo-native validation commands and generated/vendor boundaries.
- Permission for removals or cross-surface cleanup when needed.
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.
- 8d ago First seen · 143 lines · 33 tokens per session scan A 3cd010ca7c1c
unslopify is a skill published in the GitHub repository jscraik/Agent-Skills (8 stars, last pushed 10d ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,163 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
prepare-pr
A pull-request preparation workflow for a software branch. A pull request is a request for teammates to review and merge a set of code changes.
refactoring
Safely refactor code while maintaining behavior. Use when improving code structure, reducing duplication, extracting functions, or modernizing legacy code.
code-review
Automated code review for pull requests using specialized review patterns. Analyzes code for quality, security, performance, and best practices. Use when reviewing code changes, PRs, or doing code audits.
doubt-driven-development
Subjects every non-trivial decision to a fresh-context adversarial review before it stands. Use when correctness matters more than speed, when working in unfamiliar code, when stakes are high (production, security-sensitive logic, irreversible operations), or any time a confident output would be cheaper to verify now…
pr-review-expert
Review GitHub PRs or GitLab MRs for correctness, security, compatibility, and affected test coverage, with actionable evidence tied to the diff.
magpie-reviewer-routing
Given an open issue or PR, scores the project's configured reviewer roster across three signals — touched-area eligibility, git-history familiarity with the changed paths, and current open-review load — and proposes a primary reviewer (plus an optional backup). Read-only and propose-then-confirm: nothing is assigned…