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/release-notes/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/release-notes)<a href="https://agentmods.dev/skills/ccch1mneyyy/dsh-tui/release-notes"><img src="https://agentmods.dev/badge/skills/ccch1mneyyy/dsh-tui/release-notes/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/release-notes"><img src="https://agentmods.dev/badge/skills/ccch1mneyyy/dsh-tui/release-notes.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.00254 |
| Opus 5.5 | $0.00016 | $0.00102 |
| Sonnet 5.5 | $0.00008 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00025 |
Grade A, and why
release-notes 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
Explain what changes for users in the requested release, in their language.
- Use the user's specified range. Otherwise identify the target version and the previous published release on the relevant stable or prerelease line; do not assume the newest Git tag is the right baseline. State any uncertainty before describing changes as released.
- Inspect the net diff and associated commits or PRs. Account for reverts and fixes folded into the same release; do not turn every commit into a separate feature.
- Lead with breaking changes, if any, and concrete migration steps. Group the remaining user-visible changes only where that helps scanning. Omit empty sections and internal churn with no user impact.
- Use verified PR links and contributor credits, following the repository's release-note format. Keep benefits, limitations, and availability tied to the actual change; do not invent release status or migration instructions.
Deliver the notes as a draft unless publishing is part of the user's request. If it is, continue the authorized release workflow using the repository's version and tag rules.
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 · -12 lines · +3 tokens per session 38c31c37b9db
- 1mo ago First seen · 26 lines · 36 tokens per session scan A ad13de99bb40
release-notes 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 254 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
dsh-promote-deployment
Use when promoting the running DSH deployment to a new release, building or switching a release mirror, restarting the supervisor that serves it, or diagnosing a deployment that reports a new version while serving old behavior. Covers the mirror build, the profile guard's acceptance step, and the runtime package…
update-v8-version
Update Codex's pinned v8 / rustyv8 versions, validate the release-candidate path, and investigate failed V8 canary or artifact builds. Use when asked to bump V8, update rustyv8 artifacts, prepare or validate a V8 release candidate, check v8-canary, or diagnose why a V8 version update no longer builds.
changelog-writing
A writing guide for maintaining a CHANGELOG.md file, which records user-visible changes between software versions. It also covers the release notes taken from the current version section.
release
Step through versioning, tagging, and verification.
release-deploy
A release and deployment skill for preparing a software project for GitHub publication and putting it online.
final-release-review
Plan, implement, or review final release review work in an existing codebase with compatibility, security, and verification controls. Use when the user explicitly requests final release review work.