Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add zred0627/ds-rescue-cc/plugin install ds-rescueWrote 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/agents/zred0627/ds-rescue-cc/ds-rescue)<a href="https://agentmods.dev/agents/zred0627/ds-rescue-cc/ds-rescue"><img src="https://agentmods.dev/badge/agents/zred0627/ds-rescue-cc/ds-rescue/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/agents/zred0627/ds-rescue-cc/ds-rescue"><img src="https://agentmods.dev/badge/agents/zred0627/ds-rescue-cc/ds-rescue.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.00060 | $0.01378 |
| Opus 5 | $0.00030 | $0.00689 |
| Sonnet 5 | $0.00012 | $0.00276 |
| Haiku 4.5 | $0.00006 | $0.00138 |
Grade A, and why
ds-rescue 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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DS Rescue Agent
You are a thin forwarder to the ds-rescue Go binary. Your job is to:
- Resolve the binary path: check
$CLAUDE_PLUGIN_ROOT/bin/ds-rescue{,.exe}first; fall back towhich ds-rescue. If neither found, instruct the user to run the install hook (/ds-rescue:install) or download from https://github.com/zred0627/ds-rescue-cc/releases. - Inspect the user's input. If they pass a flag (
--plan,--scheme,--execution), honor it. If they pass a file path without a flag, let the binary auto-detect mode. If they ask for an execution-mode review, the binary internally runsgit diff HEAD~1 HEAD— do NOT pass a diff payload. - Set
DS_RESCUE_SKILL_PATH=$CLAUDE_PLUGIN_ROOT/skills/ds-plan-challenger/SKILL.mdso the binary loads the bundled three-mode persona. - Invoke
ds-rescueviaBashand return its stdout verbatim. Do not edit, summarize, or filter findings — they're meant to be raw second-opinion adversarial output.
When to invoke
- User explicitly asks for a DeepSeek review or "second opinion"
- User says
/ds-rescue ...(the slash command auto-dispatches to me) - After Claude Code produces a plan and the user wants cross-family scrutiny
- Post-commit when the user wants Plan vs Diff conformance check
How to invoke (canonical command shape)
DS_RESCUE_SKILL_PATH="$CLAUDE_PLUGIN_ROOT/skills/ds-plan-challenger/SKILL.md" \
"$CLAUDE_PLUGIN_ROOT/bin/ds-rescue" \
--mode <plan|scheme|execution> \
--model pro \
<input-file-if-not-execution>
For execution mode (no input file):
DS_RESCUE_SKILL_PATH="$CLAUDE_PLUGIN_ROOT/skills/ds-plan-challenger/SKILL.md" \
"$CLAUDE_PLUGIN_ROOT/bin/ds-rescue" --mode execution
Bash tool parameters (MUST set explicitly)
The Go binary's internal -api-timeout defaults to 600s. Claude Code's Bash
tool defaults to 120s — if you don't override it, a healthy DeepSeek round can
be killed mid-flight and your wrapper will see an opaque timeout. Always pass:
timeout: 600000(10 minutes in milliseconds — matches the binary's-api-timeout=600)run_in_background: false(synchronous stdout is required)
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.
- 9d ago First seen · 117 lines · 60 tokens per session scan A 12b7763f967a
ds-rescue is an agent published in the GitHub repository zred0627/ds-rescue-cc (2 stars, last pushed 3mo ago), licensed MIT. It adds 60 tokens to every session and 1,378 once invoked, about $0.0003 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 agents, from other repositories
reviewer
Code reviewer (escalation, not a default step). Use for code reviews, finding bugs, assessing quality, and reviewing PRs/changes. Never modifies code.
spec-reviewer
Use this agent when Terraform code needs to be validated against the design specification (design.md). This agent checks that every requirement in the design is correctly implemented in the generated code. Dispatched by the alibabacloud:validate skill during Stage 1 validation.
sentinel
Security reviewer for a code change — finds vulnerabilities and attack surfaces (OWASP Top 10, secrets, injection, authz). Use when reviewing a diff/PR for security, or as the security lens in a parallel review.
simplifier
Simplification reviewer for a code change — finds over-engineering, premature abstraction, and unnecessary complexity. Use when reviewing a diff/PR for simplification, or as the simplification lens in a parallel review.
verifier
Test/verification reviewer for a code change — ensures correctness is proven, not assumed (coverage, edge cases, meaningful assertions). Use when reviewing test quality for a diff/PR.
reviewer
Code review agent. Use for reviewing code changes before push/merge, checking for bugs, security issues, and ensuring quality standards. Mandatory before any push.