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 decocms/studio --skill task-board-setupgit clone --depth 1 https://github.com/decocms/studioWrote 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/decocms/studio/task-board-setup)<a href="https://agentmods.dev/skills/decocms/studio/task-board-setup"><img src="https://agentmods.dev/badge/skills/decocms/studio/task-board-setup/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/decocms/studio/task-board-setup"><img src="https://agentmods.dev/badge/skills/decocms/studio/task-board-setup.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.00048 | $0.01200 |
| Opus 5.5 | $0.00019 | $0.00480 |
| Sonnet 5.5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
task-board-setup 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 yesterday.
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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
task-board-setup — set the board up with the user
You are helping the user configure their task board so each column tells the agent what to do. Interview them, propose, confirm, then apply with the tools below. Every write shows on their open board immediately.
Tools
TASK_BOARD_PROMPT_LIST/AUTOMATION_LIST— read what is set now. Call both first;AUTOMATION_GETshows an automation's starters.TASK_BOARD_PROMPT_UPSERT— a scope's standing instructions and skills.columnKeynull (omitted) = every column; a key = that column only.skillsreplaces the list; omit it to keep the current one.TASK_BOARD_PROMPT_DELETE— clear a scope.AUTOMATION_CREATEthenAUTOMATION_TRIGGER_ADDwithtype: "board_column_transition"and acolumn_key— run an agent on every unassigned card that settles in that column. The automation's message is what to do with the card there;virtual_mcp_idis the agent (the Super Agent isdecopilot_<org id>).fromnarrows it by where the card came from (any,earlier,later, orstatuses).AUTOMATION_UPDATEwithactive: false, orAUTOMATION_DELETE— stop one.
Column keys, in board order: triage (Backlog), todo, in_progress, in_review,
qa, customer_approval, ready_for_deployment, post_deploy_validation,
done, archived.
What the board already does in each, so you don't set a rule that fights it:
- To Do: ready to start; nothing runs there on its own.
- In Progress: the built-in Implementer automation (on by default) runs the Super Agent on each unassigned card that lands here, and a card delegated to the agent runs right away. Its column instructions are the implementer's working rules. A built-in can be turned off, not edited.
- In Review: opening a pull request moves the card here and the reviewer runs on it. Its column instructions are how the reviewer reviews. Don't add an automation on it.
- QA and Customer Approval: people check the work (your team, then the customer). An agent can comment on a card there but never moves it forward.
- Ready for Deployment: the card is cleared to merge; the Ship button merges it, or the board does on arrival when auto-merge is on.
- Post-deploy Validation: merged; someone confirms it in production and moves it to Done.
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.
- yesterday Changed · +2 lines · +5 tokens per session e595d1f62f64
- 2d ago Changed · +15 lines 376bc6daa14c
- 9d ago First seen · 55 lines · 43 tokens per session scan A 727a95147f66
task-board-setup is a skill published in the GitHub repository decocms/studio (409 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,200 once invoked, about $0.0002 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
pod-init
Initialize CocoPlus project bundle in the current directory. Creates .cocoplus/ directory structure, copies all templates, initializes AGENTS.md, project.md, flow.json, and creates the initial git commit. Run this once per project before using any other CocoPlus command.
cocoharvest
Decompose an approved plan into parallel workstreams, assign specialist personas, classify stages as HITL or AFK (CocoLens), generate flow.json stages with checkpoints and dual-file state, and create per-stage prompt files. Includes adaptive parallelism, stall detection, shell identity injection, and consecutive…
cococonverge
CocoPivot — multi-pod convergence synthesizer. Deterministically deduplicates findings from N parallel pod outputs into one prioritized, coordinated action plan. Invoked via $pivot run/show/status/clear.
plan
Enter the Plan phase of CocoBrew. Runs CocoSpec quality gate pre-flight, reads spec.md and discuss.md (if present), invokes Coco native plan mode as a mandatory gate, captures the approved plan to plan.md, creates initial flow.json template, and commits. Must have $spec completed first.
lean-debt
CocoLean shortcut debt ledger — harvests cocoplus: comment markers across the CocoPod and produces a ranked deferral report sorted by ceiling imminence and age.
cocoplus-config
CocoPlus configuration SSOT — $cocoplus sync propagates cocoplus.toml into downstream artifacts; $cocoplus migrate-config converts legacy safety-config.json. Invoked via $cocoplus sync and $cocoplus migrate-config.