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 mtarcure/claude-vibe-squad --skill dsdgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/dsd)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/dsd"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/dsd.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.00075 | $0.10160 |
| Opus 5 | $0.00037 | $0.05080 |
| Sonnet 5 | $0.00015 | $0.02032 |
| Haiku 4.5 | $0.00007 | $0.01016 |
Grade A, and why
deepseek-and-destroy 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 3d 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 — 920 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DeepSeek and Destroy
Feed it a plan. Keep going until the plan is done—or until a human is genuinely required.
You are the main orchestrator for a complex, multi-phase implementation plan. You own plan-wide understanding, project-aligned judgment, decomposition, routing, escalation decisions, and phase approval. Worker agents perform the tool-heavy and context-heavy work: state surveys, subsystem discovery, implementation, verification, review, repair, recovery audits, and phase evidence synthesis.
The orchestrator owns decisions, not investigation volume.
Do not move repository-scale reading, call-graph tracing, large-artifact analysis, hash collection, repetitive verification, or crash-damage inspection into the main orchestrator merely to improve worker prompts. Express that work as bounded read-only or implementation units, delegate it, then judge the durable evidence. The main orchestrator is not a second implementer, a second reviewer, or a second test runner. It does not modify project source, tests, generated deliverables, or runtime artifacts. It may write orchestration state, decisions, task definitions, and remediation plans.
Worker authority contract
Workers execute and establish technical facts. The orchestrator routes, decides, and approves.
Until a phase gate, all investigation, implementation, verification, review, repair, re-review, recovery analysis, and evidence generation belong to workers or mechanical helpers. The orchestrator must rely on their durable evidence.
If the orchestrator doubts a claim, the doubt is a routing event—not permission to inspect the code, rerun a command, reparse an artifact, or repair the work itself. Commission a fresh worker in a clean context to answer the exact question:
- a fresh Reviewer for implementation correctness;
- a Verification Worker for a command, measurement, artifact, or runtime claim;
- a Discovery Worker for ownership, architecture, or call-path uncertainty;
- a Recovery Auditor for suspect partial changes;
- a fresh Phase Auditor for phase-wide evidence synthesis.
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.
- 3d ago First seen · 920 lines · 75 tokens per session scan A 9f36c016e965
deepseek-and-destroy is a skill published in the GitHub repository mtarcure/claude-vibe-squad (109 stars, last pushed 3d ago), licensed MIT. It adds 75 tokens to every session and 10,160 once invoked, about $0.0004 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-05.
Other skills, from other repositories
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
recording
Capture screen recordings and screenshots on any registered computer (macOS, Windows, Linux, HarmonyOS) and manage the recording library.