dsh-TUI is a terminal interface plugin for DeepSeek Harness that gives the coding agent a Claude Code-style display with live status, streaming thoughts, rollback, context usage, and TPS information. It is for users who prefer a richer terminal workflow, and the catalogue entries extend the DeepSeek Harness environment with related skills and instructions.
Borrowing it
Nothing to install: this file belongs to ccch1mneyyy/dsh-TUI. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ccch1mneyyy/dsh-TUI/main/.agents/skills/bug/SKILL.mdgit clone --depth 1 https://github.com/ccch1mneyyy/dsh-TUIWrote 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/ccch1mneyyy/dsh-tui/bug)<a href="https://agentmods.dev/skills/ccch1mneyyy/dsh-tui/bug"><img src="https://agentmods.dev/badge/skills/ccch1mneyyy/dsh-tui/bug/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/skills/ccch1mneyyy/dsh-tui/bug"><img src="https://agentmods.dev/badge/skills/ccch1mneyyy/dsh-tui/bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00250 |
| Opus 5.5 | $0.00016 | $0.00100 |
| Sonnet 5.5 | $0.00008 | $0.00050 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
bug 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 1mo 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
Produce a concise report another person can reproduce or investigate. If the user asked for a fix, use the report as working context, continue the repair, and validate the result.
- Extract the symptom, expected behavior, and reproduction details already supplied. Inspect available logs and relevant code before asking for facts the workspace can provide.
- Ask only for missing information that materially affects reproduction or diagnosis, such as terminal mode or the triggering input. Continue independent investigation while waiting; label unknowns instead of guessing.
- Include the symptom in the title, then the smallest known reproduction, expected versus actual result, relevant environment, and impact. Distinguish a reproduction you ran from one reported by the user.
- Include a cause or workaround only when evidence supports it; label hypotheses and cite the relevant code. Omit empty sections and speculative severity labels.
Keep credentials and private session content out of the report. Drafting a report does not itself authorize posting an issue; use any posting authorization already given in the conversation.
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.
- 1mo ago Changed · -14 lines · +7 tokens per session 2e182f6c1302
- 1mo ago First seen · 28 lines · 33 tokens per session scan A 092cf8373706
bug is a skill published in the GitHub repository ccch1mneyyy/dsh-TUI (5,919 stars, last pushed today), licensed MIT. It adds 40 tokens to every session and 250 once invoked, about $0.0002 per session on Opus 5.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
Diagnose failures from runtime evidence before editing code.
dsh-speed-up-perf
Use when investigating or optimizing DeepSeek Harness performance, designing realistic synthetic benchmarks or CI performance gates, profiling long Sessions or Web responsiveness, or turning performance PR evidence into measured behavior-preserving fixes.
submit-dsh-plugin
A submission checklist and workflow for adding a DeepSeek Harness plugin to the community’s public catalogue. It prepares the catalogue entry and checks the plugin’s repository, metadata, tests, and required files.
webnovel-doctor
A read-only health check for web-novel projects, including their files, settings, databases, retrieval setup, dependencies, and dashboard build output.
agentdebug
Use AgentDebugX for trajectory diagnosis only when the user explicitly asks to use AgentDebug, AgentDebugX, or the agentdebug skill. Do not invoke for generic debugging, diagnosis, inspection, or trajectory-review requests.
agentdebug
Use AgentDebugX only when the user explicitly asks for AgentDebug, AgentDebugX, or the agentdebug skill. Do not invoke for generic debugging or trajectory review.