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/coven-board-entry)<a href="https://agentmods.dev/skills/opencoven/coven/coven-board-entry"><img src="https://agentmods.dev/badge/skills/opencoven/coven/coven-board-entry/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/coven-board-entry"><img src="https://agentmods.dev/badge/skills/opencoven/coven/coven-board-entry.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.00000 | $0.00699 |
| Opus 5 | $0.00000 | $0.00349 |
| Sonnet 5 | $0.00000 | $0.00140 |
| Haiku 4.5 | $0.00000 | $0.00070 |
Grade A, and why
coven-board-entry 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 10d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: coven-board-entry
Purpose: Create a new task on the Coven task board programmatically. Any familiar can use this without knowing task service internals.
Input
| Field | Type | Default | Notes |
|---|---|---|---|
title |
string | required | Task title |
description |
string | optional | Full description |
status |
TaskStatus | "inbox" |
inbox / started / completed / blocked |
priority |
TaskPriority | "medium" |
critical / high / medium / low |
familiar |
string | optional | Familiar slug (e.g. "echo") |
project |
string | optional | Project name (e.g. "CovenCave") |
tags |
string[] | optional | Array of tags |
Output
Returns the created CovenTask object as JSON.
How it works
- Try gateway API first — POST to
http://localhost:3000/api/gateway/taskswith task payload - Fallback — If gateway unavailable or fails, write to
~/.openclaw/coven-tasks-pending.jsonfor later sync
Usage (from a familiar / subagent)
# Direct call via the skill script
node /Users/buns/.openclaw/workspace/echo/skills/coven-board-entry/create-task.mjs \
--title "My new task" \
--description "Details here" \
--priority high \
--familiar echo \
--project CovenCave \
--tags memory,ui
Or via the JS API (ESM):
import { createCovenTask } from './create-task.mjs';
const task = await createCovenTask({
title: "My task",
priority: "high",
familiar: "echo",
project: "CovenCave",
tags: ["memory"]
});
console.log(task);
Notes
- IDs are auto-generated as
<familiar>-<slug>-<timestamp>ortask-<uuid> createdAt/updatedAtare set automatically to current UTC timecreatedBydefaults tofamiliarif provided, else"unknown"- Pending tasks file:
~/.openclaw/coven-tasks-pending.json
Location & Symlink Convention
Canonical source: OpenCoven/coven/skills/coven-board-entry/
This skill is symlinked into harnesses and familiar workspaces from the canonical location. Do not edit copies — edit the source.
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.
- 10d ago First seen · 78 lines · 0 tokens per session scan A b495104ab526
coven-board-entry is a skill published in the GitHub repository OpenCoven/coven (47 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 699 tokens. 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.
swarm-orchestration
Multi-agent swarm formation and coordinated execution with topology-aware agent deployment, consensus protocols, and anti-drift enforcement.