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 hekmon8/awesome-claude-code-plugins --skill dsh-run-outputgit clone --depth 1 https://github.com/hekmon8/awesome-claude-code-pluginsWrote 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/hekmon8/awesome-claude-code-plugins/dsh-run-output)<a href="https://agentmods.dev/skills/hekmon8/awesome-claude-code-plugins/dsh-run-output"><img src="https://agentmods.dev/badge/skills/hekmon8/awesome-claude-code-plugins/dsh-run-output/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/hekmon8/awesome-claude-code-plugins/dsh-run-output"><img src="https://agentmods.dev/badge/skills/hekmon8/awesome-claude-code-plugins/dsh-run-output.svg" alt="Reviewed on agentmods" width="80" 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.00368 |
| Opus 5.5 | $0.00016 | $0.00147 |
| Sonnet 5.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 2mo 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.
This is a copy
100% identical to dsh-run-output — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 2mo ago First seen · 17 lines · 40 tokens per session scan A 76e9cc78ddb2
dsh-run-output is a skill published in the GitHub repository hekmon8/awesome-claude-code-plugins (5 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 40 tokens to every session and 368 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dsh-run-output, differing in 0 lines, and is treated as a copy.
dsh-run-output compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| dsh-run-outputhekmon8/awesome-claude-code-plugins | Skill | 5 | 1mo ago | CC0-1.0 | A | 40 | Claude Code |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |