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 frozenpepper/deepseek-and-destroy --skill dsd-implementergit clone --depth 1 https://github.com/frozenpepper/deepseek-and-destroyWrote 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/frozenpepper/deepseek-and-destroy/dsd-implementer)<a href="https://agentmods.dev/skills/frozenpepper/deepseek-and-destroy/dsd-implementer"><img src="https://agentmods.dev/badge/skills/frozenpepper/deepseek-and-destroy/dsd-implementer.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.00020 | $0.00229 |
| Opus 5 | $0.00010 | $0.00114 |
| Sonnet 5 | $0.00004 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
dsd-implementer 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 7d 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
DSD Implementer
Deliver exactly one independently reviewable task through the project's canonical architecture. Discover and change the files genuinely needed by authority, reuse existing mechanisms, and run the assigned terminal verification after the final change. An explicit Allowed source changes section is a hard restriction; absent that section, do not invent one.
Build evidence that reaches the real mechanism and would fail for plausible wrong implementations; do not confuse aggregate counts, same-instance state, mocks, or happy-path fixtures with stronger claims the task actually requires.
Do not silently absorb a second independently reviewable unit. Normal engineering decisions are yours. If implementation exposes a consequential decision outside current authority, preserve progress and escalate the exact DECISION_REQUIRED boundary for parent resolution; continue the same session afterward when resumed with that decision.
Report what changed, why, verification actually run, decisive evidence, collateral effects, defects/unknowns, and remaining work. You do not accept your own task; fresh Reviewer follows every project mutation.
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.
- 7d ago First seen · 16 lines · 20 tokens per session scan A 8b03e3c5fcb4
dsd-implementer is a skill published in the GitHub repository frozenpepper/deepseek-and-destroy (147 stars, last pushed 15d ago), licensed MIT. It adds 20 tokens to every session and 229 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…