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 hackerFish/awesome-dsh-skills --skill dsh-debug-sessiongit clone --depth 1 https://github.com/hackerFish/awesome-dsh-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/hackerfish/awesome-dsh-skills/dsh-debug-session)<a href="https://agentmods.dev/skills/hackerfish/awesome-dsh-skills/dsh-debug-session"><img src="https://agentmods.dev/badge/skills/hackerfish/awesome-dsh-skills/dsh-debug-session.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.00040 | $0.00358 |
| Opus 5 | $0.00020 | $0.00179 |
| Sonnet 5 | $0.00008 | $0.00072 |
| Haiku 4.5 | $0.00004 | $0.00036 |
Grade A, and why
dsh-debug-session 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
DSH 问题排查
先收集（一并写进求助帖）
- DSH 版本、node/pnpm 版本
- 插件清单（profile 的 package.json 依赖）
- 完整报错与日志、复现步骤
排查顺序
dsh --profile web --dump-config：确认插件层是否真的进入配置- 看启动日志：报错是否指向某个插件
- 二分法：移除最近安装的插件 → 重启 → 确认是否恢复
- 检查安装摩擦：pnpm 9 需
--ignore-workspace-root-check；大依赖树直连超时换 npmmirror；git 插件 prepare 需 allowBuilds 放行 - 版本漂移：核对插件测试时的 DSH 版本与当前版本（参考 dsh-lab 报告）
备份与回滚
- 改配置前备份
$DSH_HOME/profiles/<名字>/（核心是 package.json 与 cordis.patch.yml） - 出问题先恢复到备份状态，再逐项重放改动
求助
官方 GitHub Discussions 是明示关注的渠道；发帖附上前面的信息，描述"期望 vs 实际"。
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 · 31 lines · 40 tokens per session scan A cc43ed087a66
dsh-debug-session is a skill published in the GitHub repository hackerFish/awesome-dsh-skills (5 stars, last pushed 3d ago), licensed MIT. It adds 40 tokens to every session and 358 once invoked, about $0.0002 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
dsh-troubleshoot
A troubleshooting guide for DeepSeek Harness, including its process, configuration, plugins, tools, skills, and model connections.
ask-good-questions
Guidance for asking technical questions and reporting bugs so another developer can reproduce and answer them. It covers versions, environment details, minimal reproduction steps, expected and actual results, errors, and attempted fixes.
error-handling
A set of rules for deciding how software should report failures and what information error messages should contain.
debug-systematically
A structured method for finding the underlying cause of a software problem. It moves from reproducing the problem, to locating the responsible code, to testing a specific explanation, and then to fixing it with a regression test.
perf-optimize
A performance-improvement guide that requires measuring real behaviour before changing code. It explains how to identify bottlenecks, test one change at a time, and check that the change did not break anything.
diagnosing-bugs
A structured workflow for finding the cause of difficult bugs and performance slowdowns. It first builds a small, repeatable check that clearly shows whether the problem is present, then uses tests, scripts, traces, or comparisons to investigate it.