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 Dragoon0x/dragoon-skills --skill slopgit clone --depth 1 https://github.com/Dragoon0x/dragoon-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/dragoon0x/dragoon-skills/slop)<a href="https://agentmods.dev/skills/dragoon0x/dragoon-skills/slop"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/slop/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/dragoon0x/dragoon-skills/slop"><img src="https://agentmods.dev/badge/skills/dragoon0x/dragoon-skills/slop.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.00148 | $0.00585 |
| Opus 5 | $0.00074 | $0.00293 |
| Sonnet 5 | $0.00030 | $0.00117 |
| Haiku 4.5 | $0.00015 | $0.00059 |
Grade A, and why
slop 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 10d 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
/slop
The viral hook of dragoon. Detects the patterns that betray AI-generated UI: 7 different shadow values, generic violet-to-pink gradients, transition-all-duration-200 everywhere, lorem ipsum left in source, off-grid spacing, off-palette colors.
When to use
Run /slop when:
- The user wants to check if code "looks AI-generated" or "feels off"
- Reviewing a PR or diff before merging
- After a feature lands, to catch slop before it ships
- The user says "find the slop", "scan for AI tells", "audit for design hygiene"
How it works
12 deterministic rules. Each rule:
- Returns concrete findings with line, column, snippet, message, and fix
- Has a severity (low / medium / high)
- Is unit-tested
Two rules become codebase-aware when dragoon.json is present:
slop-006spacing-off-grid uses your detected gridslop-007hardcoded-color-off-palette uses your detected palette
So /slop gives generic results without /scan, and project-specific results with it. Always run /scan first if you can.
Run it
node ~/.claude/skills/dragoon/skills/slop/scripts/slop.js [path]
Flags:
--manifest <p>use a specific dragoon.json (auto-detects ./dragoon.json otherwise)--jsonmachine-readable--severity <low|medium|high>filter--ruleslist all rules and exit--quietonly show findings, no summary--helpfull usage
Exit codes
0no findings1findings present (good for CI gating)2bad usage
All rules
Run node ~/.claude/skills/dragoon/skills/slop/scripts/slop.js --rules for the full list with descriptions.
What ships with it
1 file 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.
- 10d ago First seen · 55 lines · 148 tokens per session scan A 4ed67659b218
slop is a skill published in the GitHub repository Dragoon0x/dragoon-skills (4 stars, last pushed 4mo ago), licensed MIT. It adds 148 tokens to every session and 585 once invoked, about $0.0007 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-31.
Other skills, from other repositories
ss-learn
Capture a human-approved UI design lesson as a privacy-minimized local StyleSeed candidate, review it, and prepare an opt-in share package without transmitting project code, prompts, screenshots, or brand data. Use when a person asks StyleSeed to remember, learn from, generalize, review, or prepare a reusable rule…
ss-lint
Quick automated lint — detects common design system violations in seconds.
ss-review
Review UI code for design system compliance, accessibility, and best practices.
design-system-tokens
Design token management with the W3C Design Token spec, three-tier hierarchy (global/alias/component), OKLCH color, Style Dictionary transforms, and dark mode theming. Use when creating token files, implementing theme systems, or building design-to-code pipelines.
figma-extract-design-system
Extract a design system from vibe-coded production apps that never had one: inventory components, mine de-facto styling into DTCG tokens, scaffold a Storybook package, port components, and optionally round-trip tokens/components into Figma. Use when the user wants to 'extract a design system', 'create a design system…
figma-version-history
List a Figma file's version history, snapshot the file at any past version, and diff two versions (added/removed/renamed pages plus deep per-component changes). Use when the user wants to inspect Figma history — triggers: 'list Figma versions', 'what versions does this file have', 'show version history', 'snapshot…