Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/skills/opencoven/coven/familiar-board-stewardship)<a href="https://agentmods.dev/skills/opencoven/coven/familiar-board-stewardship"><img src="https://agentmods.dev/badge/skills/opencoven/coven/familiar-board-stewardship/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/opencoven/coven/familiar-board-stewardship"><img src="https://agentmods.dev/badge/skills/opencoven/coven/familiar-board-stewardship.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.00018 | $0.01117 |
| Opus 5 | $0.00009 | $0.00558 |
| Sonnet 5 | $0.00004 | $0.00223 |
| Haiku 4.5 | $0.00002 | $0.00112 |
Grade A, and why
familiar-board-stewardship 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 11d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Familiar Board Stewardship
Use when a Coven familiar starts work, finishes work, receives durable work, finds follow-up work, or prepares a handoff.
Default rule
The Coven board is the shared operational surface. Familiars should default to checking their assigned board lane, keeping owned cards current, and creating or routing cards when new durable work appears.
This skill is runtime-portable. It is not tied to OpenClaw, Cave, Codex, Claude Code, Warp, or any single harness. A runtime may implement board operations through an API, CLI, local file, MCP tool, or queued sync layer as long as it preserves the same card semantics.
Start-of-work check
- List active board cards for the familiar's agent id and relevant project.
- Prefer existing assigned cards over inventing new work.
- Claim or mark the card active before doing substantial work when the runtime supports claims.
- If the work is not represented on the board and is durable, create a card with clear acceptance criteria.
During work
- Update the card when scope changes, blockers appear, or follow-up cards are created.
- Decompose vague parent cards into concrete children before dispatching or executing.
- Route work according to familiar lane:
- Astra: strategy, business map, priorities, decisions, routing.
- Charm: outward-facing language, outreach drafts, public narrative.
- Sage: research, evidence, synthesis, legal/process background.
- Cody: code implementation and verification.
- Kitty: general execution support, cleanup, release readiness, operational sweeps.
- Echo: continuity, retrospection, memory promotion, pattern review.
- Nova: orchestration, system changes, board hygiene, cross-lane routing.
- Salem: guardian and watch — Coven health, session and daemon posture, claims and locks, protected boundaries, and precise escalation.
Roster canon
The eight lanes above are the canonical familiar roster: Astra, Charm, Sage, Cody, Kitty, Echo, Nova, Salem. Route board work to exactly these owners.
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.
- 11d ago First seen · 133 lines · 18 tokens per session scan A 432eab597341
familiar-board-stewardship is a skill published in the GitHub repository OpenCoven/coven (47 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 1,117 once invoked, about $0.0001 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
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
mission-control
Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.
babysit-babysitter-issues
This skill should be used when the user asks to "babysit issues", "work on assigned issues", "check a5c-agent issues", "process babysitter issues", or wants to find and work on open GitHub issues assigned to a5c-agent in the babysitter repo.
project-tasks
Use this protocol to create, update, execute, or complete the structured projecttasks backlog in a Project conversation.
anti-drift
Hierarchical coordination and drift detection with frequent checkpoints, shared memory coherence validation, role specialization enforcement, and short task cycles.