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 robrohan/claude-skills --skill kanbanboardgit clone --depth 1 https://github.com/robrohan/claude-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/robrohan/claude-skills/kanbanboard)<a href="https://agentmods.dev/skills/robrohan/claude-skills/kanbanboard"><img src="https://agentmods.dev/badge/skills/robrohan/claude-skills/kanbanboard/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/robrohan/claude-skills/kanbanboard"><img src="https://agentmods.dev/badge/skills/robrohan/claude-skills/kanbanboard.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.00032 | $0.01386 |
| Opus 5 | $0.00016 | $0.00693 |
| Sonnet 5 | $0.00006 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00139 |
Grade C, and why
kanban scanned grade C with 1 finding 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
2. Find the task matching `<task name>` in `## 👨💻 Doing` 3. Review the work that was done and confirm it is complete 4. If complete: - Change `- [ ]` to `- [x]` - Move the task from `## 👨💻 Doing` to `## ✅ Done` und How it starts
The opening of the file, as written. The whole thing — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban Board
You are managing an Obsidian-format Kanban board. Parse $ARGUMENTS to determine your role and act accordingly.
The <board-file> argument is optional in all subcommands. If omitted, default to ./KANBAN.md in the current working directory.
Usage
/kanban view [board-file]
/kanban init [board-file]
/kanban plan [board-file]
/kanban manage [board-file]
/kanban work pop <agent-name> [board-file]
/kanban verify "<task name>" [board-file]
Board Format
The board file uses this structure:
---
kanban-plugin: board
---
## 🧊 Backlog
- [ ] Task 1
- [ ] Task 2 @{2027-06-20}
## 📝 Todo
- [ ] Task 3 @{2026-03-31}
- [ ] Task 4 [[Link To Obsidian File]]
## 👨💻 Doing (2)
- [ ] Task 5
- [ ] Task 6
## ✅ Done
**Complete**
- [x] Task 7
Rules for All Subcommands
- Never delete tasks — only move them forward through columns
- Always preserve the
kanban-plugin: boardfrontmatter - Always preserve all column headers exactly as written
- Always preserve the
**Complete**marker in the Done column - Only modify the column(s) relevant to your subcommand
Subcommands
view
Role: Viewer — display the board as a formatted table.
Arguments: view [board-file]
- Read the board file at the given path
- Parse all tasks from each column
- Output a markdown table with one column per stage:
| 🧊 Backlog | 📝 Todo | 👨💻 Doing | ✅ Done |
|---|---|---|---|
| Task A | Task C | Task D #agent | Task F |
| Task B | Task G |
- Each cell contains the task description (strip the
- [ ]/- [x]prefix) - Strip
#agenttags and show them in parentheses after the task:Task D (worker1) - Strip
@{date}and show dates in parentheses after the task:Task B (2027-06-20) - If a column is empty, show
—in its first cell - Do not modify the board file
init
Role: Initializer — create a new empty board file for a project.
Arguments: init <board-file>
- Check that
<board-file>does not already exist — if it does, stop and warn the user rather than overwriting their board - Create the file at the given path with this exact content:
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 · 190 lines · 32 tokens per session scan C 1de8342b8622
kanban is a skill published in the GitHub repository robrohan/claude-skills (1 stars, last pushed 6mo ago), licensed MIT. It adds 32 tokens to every session and 1,386 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".