Vibe Kanban is a task-planning and workspace tool where coding agents carry out work on branches with terminals and development servers. Teams and individual developers use kanban issues to assign tasks, review changes, preview applications, and create pull requests across supported agents. The catalogue contains instructions for using it with coding agents.
Borrowing it
Nothing to install: this file belongs to BloopAI/vibe-kanban. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BloopAI/vibe-kanban/main/AGENTS.mdgit clone --depth 1 https://github.com/BloopAI/vibe-kanbanWrote 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/instructions/bloopai/vibe-kanban/agents-md)<a href="https://agentmods.dev/instructions/bloopai/vibe-kanban/agents-md"><img src="https://agentmods.dev/badge/instructions/bloopai/vibe-kanban/agents-md/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/instructions/bloopai/vibe-kanban/agents-md"><img src="https://agentmods.dev/badge/instructions/bloopai/vibe-kanban/agents-md.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.01005 | $0.01005 |
| Opus 5.5 | $0.00402 | $0.00402 |
| Sonnet 5.5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
vibe-kanban AGENTS.md 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cdesktop AGENTS.md — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
crates/: Rust workspace crates —server(API + bins),db(SQLx models/migrations),executors,services,utils,git(Git operations),api-types(shared API types for local + remote),review(PR review tool),deployment,local-deployment,remote.packages/local-web/: Local React + TypeScript app entrypoint (Vite, Tailwind). Shell source inpackages/local-web/src.packages/remote-web/: Remote deployment frontend entrypoint.packages/web-core/: Shared React + TypeScript frontend library used by local + remote web (packages/web-core/src).shared/: Generated TypeScript types (shared/types.ts,shared/remote-types.ts) and agent tool schemas (shared/schemas/). Do not edit generated files directly.assets/,dev_assets_seed/,dev_assets/: Packaged and local dev assets.npx-cli/: Files published to the npm CLI package.scripts/: Dev helpers (ports, DB preparation).docs/: Documentation files.
Crate-specific guides
crates/remote/AGENTS.md— Remote server architecture, ElectricSQL integration, mutation patterns, environment variables.docs/AGENTS.md— Mintlify documentation writing guidelines and component reference.packages/local-web/AGENTS.md— Web app design system styling guidelines.
Managing Shared Types Between Rust and TypeScript
ts-rs allows you to derive TypeScript types from Rust structs/enums. By annotating your Rust types with #[derive(TS)] and related macros, ts-rs will generate .ts declaration files for those types.
When making changes to the types, you can regenerate them using pnpm run generate-types
Do not manually edit shared/types.ts, instead edit crates/server/src/bin/generate_types.rs
For remote/cloud types, regenerate using pnpm run remote:generate-types
Do not manually edit shared/remote-types.ts, instead edit crates/remote/src/bin/remote-generate-types.rs (see crates/remote/AGENTS.md for details).
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 · 59 lines · 1,005 tokens per session scan A c82e8bb68b45
vibe-kanban AGENTS.md is an instructions file published in the GitHub repository BloopAI/vibe-kanban (28,481 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,005 tokens to every session, about $0.0040 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.