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 agentmods add skills/cpj-dev/dsh-plugin-cc/dsh-run-outputnpx skills add cpj-dev/dsh-plugin-cc --skill dsh-run-outputgit clone --depth 1 https://github.com/cpj-dev/dsh-plugin-ccWrote 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/cpj-dev/dsh-plugin-cc/dsh-run-output)<a href="https://agentmods.dev/skills/cpj-dev/dsh-plugin-cc/dsh-run-output"><img src="https://agentmods.dev/badge/skills/cpj-dev/dsh-plugin-cc/dsh-run-output.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 | $0.00040 | $0.00368 |
| Opus 5 | $0.00020 | $0.00184 |
| Sonnet 5 | $0.00008 | $0.00074 |
| Haiku 4.5 | $0.00004 | $0.00037 |
Grade A, and why
dsh-run-output 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 5d 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
Presenting dsh run output
The bridge renders final text intended for the user. Presentation rules:
- Show the bridge's rendered output verbatim — do not paraphrase findings or re-rank severities. Your own assessment, when the user asks for it, goes after the verbatim output and is clearly attributed to you.
- Always preserve the footer metadata line (
run: <id> · dsh session: <id> · mode: ...). The run id is how the user gets back to this result; the session id is how they continue it. - For background starts, the only content that matters is the run id and the "check /dsh:runs" pointer. Keep it to one short paragraph.
- For failures, show the error message and the log path, then a one-line diagnosis of whether the failure is environmental (missing dsh, credentials, profile) or task-level (the model's turn failed). Suggest
/dsh:checkonly for environmental failures. - A critique rendered as "unstructured output" means the JSON contract failed but the review text is intact — present it as a normal review and note the formatting miss in one clause, not a paragraph.
- Never dump raw JSON (
--jsonpayloads) at the user unless they asked for JSON. - Keep bridge output verbatim so run IDs, diagnostics, commands, paths, and status values remain exact. When the user's language is not English, add any explanation in the user's language after the verbatim block; do not translate machine-facing values.
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.
- 5d ago First seen · 17 lines · 40 tokens per session scan A 76e9cc78ddb2
dsh-run-output is a skill published in the GitHub repository cpj-dev/dsh-plugin-cc (107 stars, last pushed 9d ago), licensed MIT. It adds 40 tokens to every session and 368 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-30.
Other skills, from other repositories
odai
Skill "odai" from orziz/odai, covering 精神内核, 当前判断, 按表现分配支撑, 共同行动边界 and 完成.
ribao
日报、周报、工作总结、状态更新：基于可核证事实形成完整汇报。用户要求汇报一段时期的工作、沿用既有汇报模板、整理进展与风险，或 odai 判断专业汇报工艺会改善结果时使用。.
dev-qa
开发与质量阶段——开发实现 + QA 测试 + 安全审计（职责分离）。流水线第 4 阶段，覆盖环节⑤⑥⑦。设计确认后自动调用。.
promotion
宣传与冷启动阶段——默认不生成任何宣传物料，只询问用户要不要做、做什么样的；未获明确答复就直接跳过。流水线第 6 阶段，覆盖环节⑩。部署完成后自动调用。.
idea-validation
想法验证阶段——调研市场/竞品/技术可行性，确认想法值不值得做。流水线第 1 阶段，覆盖环节①。用户说出想法后自动调用。.
product-prd
产品定义与需求阶段——产品定位 + PRD 需求文档（每条需求带验收标准）。流水线第 2 阶段，覆盖环节②③。想法验证通过后自动调用。.