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.
git clone --depth 1 https://github.com/MrZoyo/deslop-GPTWrote 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/plugins/mrzoyo/deslop-gpt/marketplace)<a href="https://agentmods.dev/plugins/mrzoyo/deslop-gpt/marketplace"><img src="https://agentmods.dev/badge/plugins/mrzoyo/deslop-gpt/marketplace/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/plugins/mrzoyo/deslop-gpt/marketplace"><img src="https://agentmods.dev/badge/plugins/mrzoyo/deslop-gpt/marketplace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
deslop marketplace 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 5d 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
{
"$schema": "https://json.schemastore.org/claude-code-marketplace.json",
"name": "deslop",
"owner": {
"name": "MrZoyo",
"url": "https://github.com/MrZoyo"
},
"description": "Claude Code distribution for the deslop Agent Skill.",
"plugins": [
{
"name": "deslop",
"source": {
"source": "url",
"url": "https://github.com/MrZoyo/deslop-GPT.git",
"ref": "v0.3.2",
"sha": "0cc15c036b07691c600bda1219b8cc5c197ca3f1"
},
"description": "Audit or apply test-first, evidence-backed cleanup for accumulated test, verification, and fallback bloat."
}
]
}
The plugins it lists here
This marketplace lists 1 plugin kept in the same repository. Each has its own page, its own measurements and its own install command.
What ships with it
1 file beside marketplace.json 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.
- 5d ago Changed 68759b082dae
- 6d ago Changed · +5 lines 474c26ec7779
- 10d ago First seen · 17 lines scan A f7b1f7708872
deslop marketplace is a plugin published in the GitHub repository MrZoyo/deslop-GPT (124 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
hunch
A git-native reasoning graph of decisions, bugs, and invariants for your codebase — queried and enforced at reasoning time. Adds the hunch MCP tools plus /hunch:capture, /hunch:heal, /hunch:why, /hunch:fix, /hunch:fragile.
catenary
Enforced code intelligence for Claude Code — an opinionated, LSP-backed command surface (grep, glob, sed, diagnostics) plus a hook that keeps the agent on the code-intelligent path.
kin
Kin keeps a living map of the software itself so humans and agents can understand what every change touches. Locate, search, context packs, data-flow tracing, and impact analysis without raw file search.
memtrace-skills
Memtrace skills for codebase exploration, code search, relationship analysis, temporal evolution, blast radius impact, code quality, graph algorithms, API topology, GitHub PR code review, multi-agent fleet coordination (branch-scoped intents, conflict classification, and agent-judged Class C resolution), and…
forensic-deepdive
Persistent code knowledge graph + 9 composite MCP tools (impact, context, archaeology, flow, query, recordinsight, recallinsights, visualize, trace) for AI coding agents.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.