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 itechmeat/llm-code --skill vibekanbangit clone --depth 1 https://github.com/itechmeat/llm-codeWrote 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/itechmeat/llm-code/vibekanban)<a href="https://agentmods.dev/skills/itechmeat/llm-code/vibekanban"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/vibekanban/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/itechmeat/llm-code/vibekanban"><img src="https://agentmods.dev/badge/skills/itechmeat/llm-code/vibekanban.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 37 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 40 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 79 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 90 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00074 | $0.02328 |
| Opus 5.5 | $0.00030 | $0.00931 |
| Sonnet 5.5 | $0.00015 | $0.00466 |
| Haiku 4.5 | $0.00007 | $0.00233 |
Grade A, and why
vibekanban 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 1mo 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Kanban
Orchestration platform for AI coding agents. Plan, review, and manage AI-generated code in isolated git worktrees.
Links
Quick Navigation
| Topic | Reference |
|---|---|
| Installation & Setup | getting-started.md |
| Workspaces (Beta) | workspaces.md |
| Projects, Tasks, Review | core-features.md |
| Subtasks, Attempts, Conflicts | advanced-features.md |
| Settings, Agents, Tags | configuration.md |
| GitHub, Azure, VSCode, MCP | integrations.md |
| Common Issues | troubleshooting.md |
| Best Practices | vibe-guide.md |
Quick Start
Install & Run
npx vibe-kanban
npx vibe-kanban remains the canonical cross-platform launch path. As of v0.1.30, the packaged desktop app is moving onto a Tauri v2 shell with built-in auto-update behavior for installed desktop builds.
Release Highlights (0.1.15 → 0.1.28)
- MCP server expanded: richer issue retrieval (
get_issueincludes tags/relationships/sub-issues) and new workspace/relationship/tag tools (e.g.update_workspace, relationship + tag mutations). - Frontend routing migrated to TanStack Router (navigation/URLs may differ from older screenshots).
- Reliability improvements around Electric fallback and cancellation/tab-switch handling.
- Review/diff UI improvements (annotation width fixes for horizontal scrolling).
- Remote Access: pair a host via a code and access its workspaces from another device.
- Workspace actions became safer around spin-off/duplicate flows by preserving branch and executor configuration more reliably.
- Active agent runs can now accept image attachments, which is useful when feeding UI state, screenshots, or design feedback back into an in-progress session.
- Transport reliability improvements: better relay disconnect handling and signing-session refresh.
- Claude: bumped the default Sonnet model to 4.6.
- Worktrees: preserve worktree path across cleanup to maintain Claude Code session continuity.
- Workspaces: improved workspace logs capture (root execution-process provider).
- Mobile UI fixes and Remote Access docs refresh.
What ships with it
8 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.
- 1mo ago First seen · 284 lines · 74 tokens per session scan A 9558bbbae4f2
vibekanban is a skill published in the GitHub repository itechmeat/llm-code (24 stars, last pushed 24d ago), licensed MIT. It adds 74 tokens to every session and 2,328 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
remove
Remove a deployed framework or addon from the current workspace.