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 jamesdawsonWD/mooboard-skills --skill mooboard-create-kanbangit clone --depth 1 https://github.com/jamesdawsonWD/mooboard-skillsWrote 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/jamesdawsonwd/mooboard-skills/mooboard-create-kanban)<a href="https://agentmods.dev/skills/jamesdawsonwd/mooboard-skills/mooboard-create-kanban"><img src="https://agentmods.dev/badge/skills/jamesdawsonwd/mooboard-skills/mooboard-create-kanban/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/jamesdawsonwd/mooboard-skills/mooboard-create-kanban"><img src="https://agentmods.dev/badge/skills/jamesdawsonwd/mooboard-skills/mooboard-create-kanban.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.00046 | $0.01111 |
| Opus 5 | $0.00023 | $0.00556 |
| Sonnet 5 | $0.00009 | $0.00222 |
| Haiku 4.5 | $0.00005 | $0.00111 |
Grade A, and why
mooboard-create-kanban 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mooboard Create Kanban
Create a new board under the Mooboard library as a kanban board (status columns) on an infinite board.
Core idea
Columns are statuses. Cards live inside columns. The canvas is infinite, so columns may be wide and tall; do not crush cards.
Do not rely on a layout script. Use multi-agent review.
Best use cases
- Personal / team task boards
- Hiring pipelines
- Content production stages
- Bug triage
- Sales / lead stages
Style rules
Usually includes:
- 3–6 status columns (e.g. Backlog → Doing → Review → Done)
- column headers as native text
- cards as todos, notes, links, or small images
- optional WIP limits noted under headers
- one board-level title
It should not look like a free collage or a dense document.
Layout character
Desired feel
- Clear vertical lanes
- Scanable cards
- Consistent card width inside a column
Default pattern
- Title top-left
- Column headers in a row
- Cards stacked top→bottom inside each column
- Optional “Icebox” or “Blocked” column on the far right
Spacing expectations
- Gap between columns: 140–220px
- Gap between cards in a column: 60–100px
- Hard minimum gap: 50px
- Typical card size: todo ~280×180, link 260×200, note text as needed
Required multi-agent workflow
Agent 1 — Workflow Designer
Defines statuses and what belongs in each.
Agent 2 — Column Planner
Sets column x positions and widths.
Agent 3 — Card Planner
Creates cards and assigns columns/order.
Agent 4 — Collision Auditor
Ensures cards stay inside their lane visually and do not overlap.
Agent 5 — Flow Critic
Checks whether the pipeline tells a coherent work story.
Final Manifest Reviewer
Checks the written .mooboard.json:
- coordinates match the approved plan
- every image is
presentation: "interactive" - every link is
previewMode: "card"withpreviewImage - folder media matches referenced paths exactly
Workflow
Kanban Progress:
- [ ] 1. Confirm theme, statuses, board name
- [ ] 2. Gather cards (tasks, links, images)
- [ ] 3. Place column headers
- [ ] 4. Stack cards per column
- [ ] 5. Multi-agent review
- [ ] 6. Write .mooboard.json
- [ ] 7. Remove orphan media; final review
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 · 167 lines · 46 tokens per session scan A dccb6af4c960
mooboard-create-kanban is a skill published in the GitHub repository jamesdawsonWD/mooboard-skills (5 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 1,111 once invoked, about $0.0002 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-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.