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 dwarvesf/dwarves-kit --skill kit-boardgit clone --depth 1 https://github.com/dwarvesf/dwarves-kitWrote 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/dwarvesf/dwarves-kit/kit-board)<a href="https://agentmods.dev/skills/dwarvesf/dwarves-kit/kit-board"><img src="https://agentmods.dev/badge/skills/dwarvesf/dwarves-kit/kit-board/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/dwarvesf/dwarves-kit/kit-board"><img src="https://agentmods.dev/badge/skills/dwarvesf/dwarves-kit/kit-board.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.00097 | $0.00618 |
| Opus 5.5 | $0.00039 | $0.00247 |
| Sonnet 5.5 | $0.00019 | $0.00124 |
| Haiku 4.5 | $0.00010 | $0.00062 |
Grade A, and why
kit-board 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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kit-board
The kit owns the logic. This skill only says which command answers which question. Run it in the terminal, read the output, answer in plain words. Do not recompute anything the command already printed.
question command (all read-only)
--------------------------------- ------------------------------------------------------
how are the boards / over limit ~/.claude/dwarves-kit/bin/board health run --dry-run --force
what needs my decision, the brief ~/.claude/dwarves-kit/bin/board brief run --dry-run --force --show-boards
backlog rows across repos ~/.claude/dwarves-kit/bin/board status
what is the sweep doing ~/.claude/dwarves-kit/bin/board sweep verify --last-tick
When to use
- A question about board counts, stale or waiting cards, sync health, or what the daily brief says.
- A request to explain one line of a brief you were shown.
How to answer
- Run the command from the table. The operator's flags come from the kit config file (
$DWARVES_BOARD_CONFIG, else~/.config/dwarves-kit/board.json), so no flags beyond the ones shown are needed. - Each output line is one JSON payload per cluster. The lines you read are in
.fields[].value;briefpayloads also carry.details. - A board over its threshold is a field that reads
<board>: N waiting in triage, oldest Nd, and a line+N more boards over thresholdwhen there are more than three. Count those. No such field means no board is over threshold. - A
needs your decisionblock lists questions for the operator. Repeat them as asked. Never answer one yourself. - Say what you ran in one short line, then the answer.
Never
- Never run
board brief runorboard health runwithout--dry-run: a real run posts to a channel and stamps state. - Never edit
_meta/BACKLOG.md, a kanban card, or the config file from here. - Never print a token or a webhook if one shows in an error. Say the command failed and quote the first line with the secret removed.
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 First seen · 47 lines · 97 tokens per session scan A 05260d2513a9
kit-board is a skill published in the GitHub repository dwarvesf/dwarves-kit (12 stars, last pushed today), licensed MIT. It adds 97 tokens to every session and 618 once invoked, about $0.0004 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-07.
Other skills, from other repositories
project-specification
Transforms project briefs into testable specifications with user stories and acceptance criteria. Use after brainstorming, before planning.
multi-agent
A process for coordinating multiple coding agents by splitting work among scouts, workers, reviewers, and repair agents. Each agent has a defined role and task.
gsd-new-project
Initialize a new project with deep context gathering and PROJECT.md.
gsd-resume-work
Resume work from previous session with full context restoration.
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…