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/dip497/hivemind/adding-an-agent-providernpx skills add dip497/hivemind --skill adding-an-agent-providergit clone --depth 1 https://github.com/dip497/hivemindWrote 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/dip497/hivemind/adding-an-agent-provider)<a href="https://agentmods.dev/skills/dip497/hivemind/adding-an-agent-provider"><img src="https://agentmods.dev/badge/skills/dip497/hivemind/adding-an-agent-provider.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.00084 | $0.02889 |
| Opus 5 | $0.00042 | $0.01444 |
| Sonnet 5 | $0.00017 | $0.00578 |
| Haiku 4.5 | $0.00008 | $0.00289 |
Grade A, and why
adding-an-agent-provider 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Adding an agent provider
Why this exists
docs/agent-status-signals.md already tells you the three files to edit. That is not
where provider PRs go wrong. They go wrong one step earlier — in what the author
believed about the CLI.
A real example: a PR added an agent and stated "no hook system exposed, status is
screen-scrape only". That CLI ships agentSpawn / userPromptSubmit / preToolUse /
postToolUse / stop hooks with a JSON stdin contract and a blocking exit code — the
same shape hivemind already consumes for claude. Nobody had run --help. The result
would have shipped as a "fully-wired agent" that silently cannot be driven: hive_read
returns timeout forever, hive_workflow gathers nothing, and a tile parked on an
approval prompt notifies "Finished".
A half-wired agent is worse than an absent one, because the failure is silent. This skill is the procedure that makes that impossible: research first, tier second, code third, and a lifecycle table that says out loud what works.
The rule
An agent is done when a human can drive it on the canvas and the control plane can drive it as a worker. If you can only reach the first, that is a legitimate PR — but it ships explicitly labelled as a manual tile, never silently.
Phase 1 — Probe the CLI (never skip, never infer)
Three rules:
- Probe the binary that is actually installed.
--helpbeats memory, every time. - Cite a source per answer — a doc URL, a
--helpline, a file you grepped. - "I could not find it" is a valid answer. Write it that way. Never write "X does not exist" unless you looked and can say where you looked. Absence claims are what reviewers check first, because they are what gets a provider shipped half-wired.
Never infer a capability from another agent's shape. Two CLIs that look alike in the TUI can differ completely in hooks, session storage, and MCP support.
which <bin>; <bin> --version; <bin> --help
<bin> <subcommand> --help # chat/run/agent — whatever the entry command is
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.
- 5d ago First seen · 213 lines · 84 tokens per session scan A 6bf575ebc040
adding-an-agent-provider is a skill published in the GitHub repository dip497/hivemind (6 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 2,889 once invoked, about $0.0004 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-31.
Other skills, from other repositories
doubt-driven-review
In-flight adversarial check on a non-trivial decision BEFORE it stands — distinct from post-hoc review of a finished diff. Use on "stress-test this decision", "are we sure about this", "verify before commit", "poke holes in this", when working in unfamiliar code, or before an irreversible step (migration, prod deploy…
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
faq-mine
Mine docs/faq.md from README.md, docs/.md, and the pi-hermes memory stores. Dispatches @fast subagents per source, dedupes against the existing FAQ, and merges entries in caveman style. Use when asked to "build / regenerate / extend the FAQ", "mine docs into FAQ", "mine hermes memory into FAQ", "surface runtime…
performance-optimization
Measure-first performance work. Use on triggers like "it's slow", "profile this", "optimize perf", "fix the bottleneck", "improve load time / Core Web Vitals", or when a measured regression needs fixing. Enforces measure-before-optimize. Fills a perf gap not covered by existing project skills. Not a build/ship…
project-init
Scaffold an unconfigured directory into a configured pi project. Interactive, profile-driven: previews the planned writes, then writes AGENTS.md, .pi/settings.json and prompt files — optionally also a knowledge base, an openspec/ scaffold, and user-global /.pi/agent/settings.json. Use on a bare directory, or when the…
plan-proposal
Develop-side planning orchestrator for an OpenSpec change: artifact creation → doubt-driven-review → scenario-design → fold of automated scenarios into tasks.md, then STOPS at the git-worktree boundary. Main interactive session only; never a subagent. Triggers: "plan this change", "draft the proposal and plan"…