hivemind: Skill for Claude Code

.claude/skills/feature-done/SKILL.md

feature-done is a skill for Claude Code from dip497/hivemind. It costs 83 tokens per session (1,120 once invoked), scanned A, original, MIT.

A checklist for deciding when a user-facing change is complete across the product's code, command-line interface, documentation, screens, and data changes. It assigns affected work to agents and defines what each surface must include.

In plain words
What is it for?
Use it before planning, briefing, or reporting a feature, command, plugin type, data change, or format change in the named open-source projects.
Why use it?
A change can work in code while remaining missing from the app, docs, or release process; this helps prevent those unfinished surfaces from being overlooked.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: reads .claude/ paths; mentions subagents.

This is dip497/hivemind's own configuration. It tells Claude Code how to work on hivemind itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything hivemind configures →

Reuse

Borrowing it

Nothing to install: this file belongs to dip497/hivemind. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/dip497/hivemind/main/.claude/skills/feature-done/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dip497/hivemind

Made for: Claude Code.

Wrote 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.

agentmods badge for feature-done

README.md
[![agentmods](https://agentmods.dev/badge/skills/dip497/hivemind/feature-done/github.svg)](https://agentmods.dev/skills/dip497/hivemind/feature-done)
Your own site
<a href="https://agentmods.dev/skills/dip497/hivemind/feature-done"><img src="https://agentmods.dev/badge/skills/dip497/hivemind/feature-done/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.

agentmods 80×15 button for feature-done

Your own site · 80×15
<a href="https://agentmods.dev/skills/dip497/hivemind/feature-done"><img src="https://agentmods.dev/badge/skills/dip497/hivemind/feature-done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,120 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00083 $0.01120
Opus 5.5 $0.00033 $0.00448
Sonnet 5.5 $0.00017 $0.00224
Haiku 4.5 $0.00008 $0.00112

Measured 9d ago against content hash ce7b74236316, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

feature-done 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 9d 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.

.claude/skills/feature-done/SKILL.md · 45 lines

How it starts

The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Feature done

Hivemind is an open-source product that people and their agents drive. A change is done when every surface below that it touches is done, not when the code compiles. The maintainer should never have to name a missing surface.

Before you start

Walk the table and write down which rows the change touches. A row that does not apply gets one word why ("no data change"). Brief every subagent with the rows it owns.

When several agents work at once, give each one the files and contracts it owns (a manifest field, a schema, a command) and its own worktree and branch. No two agents add the same field, and no agent moves or merges into another agent's branch. Ready work lands as one combined PR per round, not one PR per change.

The surfaces

# Surface Done means
1 Agent-native CLI An agent can do it end to end from hive alone: create, check, install, switch on, update, undo, inspect (--json, stable exit codes, a fix line on refusal). Nothing needs a hand-written file or a click.
2 App UI The same action exists in the app, in the place users already look, using components/ui. Checked in the running app (headless xvfb, isolated HOME) with screenshots of every state, looked at before reporting.
3 Phone and browser page Says whether the change reaches the phone/web page; if it should, it does.
4 Guide A page in site/src/content/guide/ explains it for a user, with real commands. The CLI reference (guide/(reference)/cli.mdx) and any API reference list new commands, flags, routes and shapes. One source per fact: link, never repeat.
5 Agent briefs PROMPT.md starters, hive guide, and the hivemind skill text in packages/hive-core/src/templates.ts say how an agent does it. They say how Hivemind does it and never name or ban an agent's own tools.
6 READMEs and package metadata Every README it touches names what it is and links its guide page by full URL; no stale command. homepage/repository in published packages point at the guide.
7 HiveHub If plugins, ids, kinds or the index change: HiveHub validates, lists and installs it, its site shows it, and docs/operations.md in the hub says how to deploy it. Say the deploy order when the app and the hub must change together.
8 hivemind-plugins Manifests, READMEs and dist match the new rules; its CI passes against main and the release. Merging there publishes, so say when it may merge.
9 Local data If what is on disk changes, a numbered migration ships in the same release (packages/hive-core/src/migrations/), tested on old-shaped data. Users never lose installs, settings or state.
10 Contracts and versions A changed protocol, manifest, hive ctl --json shape or CLI flag bumps its own version and gets a Breaking: CHANGELOG line. No shims for older app versions.
11 Security New input from plugins, peers, the phone or the network is checked at the boundary; secrets by name only; sandboxes hold. Address every security-review finding before reporting.
12 Tests Behaviour tests at the real boundary pass .claude/skills/test-audit/SKILL.md, each shown failing first. Locally run only the test files for what you touched, plus typecheck; CI (about 5 min, on GitHub) runs every suite on the PR, so do not repeat it on the laptop. One focused e2e for a new user flow; the full e2e runs once per round, after merge, and before a release.
13 CHANGELOG and release One line under [Unreleased] in the user's words. Release and installer steps still work (scripts/install-*-test.sh when assets or install paths change).
14 Cleanup Every worktree, shell, monitor, dev server and container you started is closed or listed. Old text, flags and code the change replaces are removed in the same change.

Read the full file on GitHub · 45 lines

Changes

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.

  1. 9d ago First seen · 45 lines · 83 tokens per session scan A ce7b74236316

Subscribe to this mod's changes

feature-done is a skill published in the GitHub repository dip497/hivemind (17 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,120 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-10-21.