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 pymc-labs/decision-hub --skill dhub-cligit clone --depth 1 https://github.com/pymc-labs/decision-hubWrote 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/pymc-labs/decision-hub/dhub-cli)<a href="https://agentmods.dev/skills/pymc-labs/decision-hub/dhub-cli"><img src="https://agentmods.dev/badge/skills/pymc-labs/decision-hub/dhub-cli.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.1 | $0.00063 | $0.03777 |
| Opus 5 | $0.00032 | $0.01888 |
| Sonnet 5 | $0.00013 | $0.00755 |
| Haiku 4.5 | $0.00006 | $0.00378 |
Grade A, and why
dhub-cli 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 413 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dhub CLI Guide
dhub is the AI skill manager for data science agents. It publishes, discovers, installs, and runs Skills — modular packages (code + prompts) that agents like Claude Code, Cursor, Codex, and Windsurf can use.
Installation
uv tool install dhub-cli # via uv (recommended)
pipx install dhub-cli # via pipx
Command Overview
dhub login Authenticate via GitHub
dhub logout Remove stored token
dhub env Show active environment, config path, API URL
dhub init [path] Scaffold a new skill project
dhub publish [ref] Publish skill(s) — from dir or git repo
dhub install org/skill Install a skill from the registry
dhub uninstall org/skill Remove a locally installed skill
dhub list List all published skills
dhub delete org/skill Delete skill versions from registry
dhub run org/skill Run a locally installed skill
dhub ask "query" Natural language skill search
dhub eval-report org/skill@version View eval report
dhub logs [ref] [-f] View or tail eval run logs
dhub org list List your namespaces
dhub config default-org Set default namespace for publishing
dhub keys add <name> Store an API key for evals
dhub keys list List stored API key names
dhub keys remove <name> Remove a stored API key
dhub doctor Check auth, API connectivity, version
dhub --version Show CLI version
dhub --output json CMD Machine-readable JSON output for any command
See references/command_reference.md for full details on every command, flag, and option.
Environments (Dev / Prod)
dhub supports two independent stacks controlled by DHUB_ENV:
| Env | API URL | Config File |
|---|---|---|
prod (default) |
https://pymc-labs--api.modal.run |
~/.dhub/config.prod.json |
dev |
https://pymc-labs--api-dev.modal.run |
~/.dhub/config.dev.json |
Always prefix commands with DHUB_ENV=dev when working against the dev stack:
What ships with it
1 file 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.
- 7d ago First seen · 413 lines · 63 tokens per session scan A 57375d9398a2
dhub-cli is a skill published in the GitHub repository pymc-labs/decision-hub (99 stars, last pushed 24d ago), licensed MIT. It adds 63 tokens to every session and 3,777 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…