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 agentmods add skills/hydro13/kanbu/openclaw-skillnpx skills add hydro13/kanbu --skill openclaw-skillgit clone --depth 1 https://github.com/hydro13/kanbuWrote 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/hydro13/kanbu/openclaw-skill)<a href="https://agentmods.dev/skills/hydro13/kanbu/openclaw-skill"><img src="https://agentmods.dev/badge/skills/hydro13/kanbu/openclaw-skill.svg" alt="Measured on agentmods" 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 | $0.00090 | $0.00910 |
| Opus 5 | $0.00045 | $0.00455 |
| Sonnet 5 | $0.00018 | $0.00182 |
| Haiku 4.5 | $0.00009 | $0.00091 |
Grade A, and why
kanbu scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For self-signed certs (local dev), the script uses `curl -k` How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanbu Skill for OpenClaw
Kanbu is a self-hosted, agent-native project management platform. This skill gives you full read/write access to Kanbu via its tRPC API.
Setup
1. Install Kanbu MCP server (includes pairing CLI)
cd /path/to/kanbu && pnpm install
2. Pair with your Kanbu instance
node packages/mcp-server/dist/index.js
On first run, the MCP server starts the pairing flow:
- It displays a setup code (6 characters)
- Go to your Kanbu instance → Settings → AI Assistants → Enter the code
- The server exchanges the code for a permanent token stored in
~/.config/kanbu/mcp.json
3. Verify
scripts/kanbu.sh workspace.list
Usage
All Kanbu operations go through the kanbu.sh wrapper script:
scripts/kanbu.sh <procedure> '<json-input>'
The script auto-detects GET (queries) vs POST (mutations) and handles auth from ~/.config/kanbu/mcp.json.
Common operations
List projects:
scripts/kanbu.sh project.list '{"workspaceId": 534}'
List tasks in a project:
scripts/kanbu.sh task.list '{"projectId": 314, "workspaceId": 534}'
Get task details:
scripts/kanbu.sh task.get '{"taskId": 307, "workspaceId": 534}'
Create a task:
scripts/kanbu.sh task.create '{"projectId": 314, "title": "Implement feature X", "description": "Details here", "priority": 2, "workspaceId": 534}'
Update a task:
scripts/kanbu.sh task.update '{"taskId": 307, "title": "Updated title", "workspaceId": 534}'
Move task to a column:
scripts/kanbu.sh task.move '{"taskId": 307, "columnId": 68, "workspaceId": 534}'
Add a comment:
scripts/kanbu.sh comment.create '{"taskId": 307, "content": "Work done.", "workspaceId": 534}'
Search tasks:
scripts/kanbu.sh search.tasks '{"query": "bug", "projectId": 314, "workspaceId": 534}'
My assigned tasks:
scripts/kanbu.sh task.getAssignedToMe '{"workspaceId": 534}'
What ships with it
2 files 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.
- 4d ago First seen · 132 lines · 90 tokens per session scan A 73455f3eb866
kanbu is a skill published in the GitHub repository hydro13/kanbu (10 stars, last pushed 6mo ago), licensed MIT. It adds 90 tokens to every session and 910 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
plan
Full execution protocol for MODE: PLAN -- plan creation, external plan ingestion, QA gate persistence, task granularity, and traceability checks.
Technical Debt Tracking with PMAT
Tracks and manages technical debt using PMAT (Pragmatic AI Labs MCP Agent Toolkit). Use this skill when: User asks about technical debt, TODO comments, or code quality issues Planning sprint work and need to prioritize debt repayment Conducting code audits or technical debt assessments Tracking debt accumulation…
release-feature-audit
Use when a new PuPu feature finishes implementation and needs its consistency audit before its ticket is marked done — "audit #123", "审计这个功能", "这个 feature 过一遍检查" — or when release-close-sprint roll-call finds a new feature that was never audited. Also covers standalone i18n checks ("漏翻了吗", "检查 i18n"), which used to be…
promote-idea
Promote an Inbox bullet from BACKLOG.md to either a GitHub issue (work commitment) or a briefing (briefings/B-NNNN-.md, research/decision support). Asks which based on whether the work is committed or still needs thinking. Removes the original bullet.
servicenow-change-management
ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use…
release-close-sprint
Use when the project owner wraps or closes a PuPu version/release — "关 0.1.10", "close the release", "版本收尾". Verifies a Size=Release parent issue and its direct sub-issues in GitHub Project, records close evidence there, and hands it to release certification.