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/pr-comments/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/pr-comments)<a href="https://agentmods.dev/skills/ccch1mneyyy/dsh-tui/pr-comments"><img src="https://agentmods.dev/badge/skills/ccch1mneyyy/dsh-tui/pr-comments/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/pr-comments"><img src="https://agentmods.dev/badge/skills/ccch1mneyyy/dsh-tui/pr-comments.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.00039 | $0.00269 |
| Opus 5.5 | $0.00016 | $0.00108 |
| Sonnet 5.5 | $0.00008 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
pr-comments 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
Turn the requested PR's review feedback into concrete next steps, using the current code to assess each concern.
- Identify the requested PR, repository, head, and base; use the current branch when no PR is specified. If no matching PR exists or access fails, report that limitation. Do not substitute a local code review for unavailable comments.
- Fetch inline threads, review summaries, and general comments, including pagination. Preserve comment links and thread resolution state. If resolution metadata is unavailable, mark it unknown.
- Read the affected code at the current PR head. Distinguish still-applicable concerns, already addressed feedback, and questions requiring a reply. A thread's resolved status and whether the code addresses it are separate facts.
- Group related feedback without losing distinct requests. Summarize each actionable concern, its evidence, and the smallest useful change; order by impact. If the user requested fixes, implement and validate them.
- Report what remains and link to the original comments. Reply, resolve threads, or post other messages only when the user has authorized those actions; summarize or draft otherwise.
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 · -8 lines · +1 tokens per session b9abe1f8702c
- 1mo ago First seen · 21 lines · 38 tokens per session scan A aa26610b191a
pr-comments is a skill published in the GitHub repository ccch1mneyyy/dsh-TUI (5,919 stars, last pushed today), licensed MIT. It adds 39 tokens to every session and 269 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
review-changes
Review local code changes for concrete correctness, regression, security, and test gaps before shipping.
dsh-code-review
Use when reviewing a pull request in the deepseek-harness repo — orients the reviewer to this codebase's standards (AGENTS.md conventions, defensive patterns, ADRs, quality gates) and the review-specific checks that code alone can't show.
dsh-find-simplifications
Use when working in the deepseek-harness repo to find non-obvious simplification candidates, remove redundant comments or implementation-heavy documentation, write proposed Agent Notes or inline TODO/FIXME/XXX notes, audit or coalesce superseded Agent Notes, or fold worthwhile simplification ideas from another PR…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
code-review
Run a final code review on a pull request.
code-review-change-size
Change size guidance (800 lines).