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 Jamie-BitFlight/claude_skills --skill dh-cli-usagegit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/dh-cli-usage)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/dh-cli-usage"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/dh-cli-usage/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/jamie-bitflight/claude_skills/dh-cli-usage"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/dh-cli-usage.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.00066 | $0.00616 |
| Opus 5.5 | $0.00026 | $0.00246 |
| Sonnet 5.5 | $0.00013 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
dh-cli-usage 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 20d 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
dh CLI usage
<sam_cli> uv run "${CLAUDE_SKILL_DIR}/../../sam_schema/cli.py" uv run "${KIMI_SKILL_DIR}/../../sam_schema/cli.py" uv run "${HERMES_SKILL_DIR}/../../sam_schema/cli.py" </sam_cli>
<dh_scripts> ${CLAUDE_SKILL_DIR}/../../scripts ${KIMI_SKILL_DIR}/../../scripts ${HERMES_SKILL_DIR}/../../scripts </dh_scripts>
Use the line whose path is absolute. A line still reading ${…} names a variable this harness does
not fill in; pass over it.
When no line is absolute, use the absolute directory the harness supplied with this skill, returned
as skill_root, or used to read this SKILL.md. Then <sam_cli/> is
uv run "<that directory>/../../sam_schema/cli.py", and <dh_scripts/> is
<that directory>/../../scripts.
When no line is absolute and no such directory is stated, report STATUS: BLOCKED naming this
skill, and run no <sam_cli/> command. Use the mcp__plugin_dh_* tools for any operation that has
one.
Wherever a dh skill, agent or reference writes <sam_cli/> plan read …, run your <sam_cli> line
followed by the words written after <sam_cli/>. The path in the line is complete; run it as
written. A path written <dh_scripts/>/name.py is your <dh_scripts> line followed by /name.py.
A dh command written without <sam_cli/>, such as plan read --address …, runs the same way: your
<sam_cli> line followed by the command.
When a <sam_cli/> command fails, run <sam_cli/> plan --help. When that also exits non-zero,
report the exact command and its stderr as STATUS: BLOCKED, and run no other <sam_cli/> command.
For the grouped commands and their options, read command reference.
When a dispatch names a ledger address and attempt, read
the runner contract before its first ledger command.
When returning or consuming an agent's response, load dh:subagent-contract for response
destination and transport status.
When an mcp__plugin_dh_* server failed to connect, read MCP connection check.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago Changed · +5 lines 832159c59c8f
- 1mo ago Changed · +4 lines 252562b1df60
- 1mo ago First seen · 41 lines · 66 tokens per session scan A 66fbbf851994
dh-cli-usage is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (67 stars, last pushed 4d ago), licensed MIT. It adds 66 tokens to every session and 616 once invoked, about $0.0003 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-09-17.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…