kanban-mcp: Skill for Claude Code

.claude/skills/kanban-review-loop/SKILL.md

kanban-review-loop is a skill for Claude Code from SimonBlancoE/kanban-mcp. It costs 27 tokens per session (1,229 once invoked), scanned A, original, MIT.

A background process that checks the health of a Kanban board, a board used to track tasks and their progress.

In plain words
What is it for?
Use it to check board health every five minutes, report problems, start QA when reviews build up, track sprint progress, and create session summaries.
Why use it?
It helps reveal escalated, stale, blocked, or overloaded work without requiring someone to inspect the board manually.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is SimonBlancoE/kanban-mcp's own configuration. It tells Claude Code how to work on kanban-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything kanban-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to SimonBlancoE/kanban-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/SimonBlancoE/kanban-mcp/main/.claude/skills/kanban-review-loop/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/SimonBlancoE/kanban-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for kanban-review-loop

README.md
[![agentmods](https://agentmods.dev/badge/skills/simonblancoe/kanban-mcp/kanban-review-loop/github.svg)](https://agentmods.dev/skills/simonblancoe/kanban-mcp/kanban-review-loop)
Your own site
<a href="https://agentmods.dev/skills/simonblancoe/kanban-mcp/kanban-review-loop"><img src="https://agentmods.dev/badge/skills/simonblancoe/kanban-mcp/kanban-review-loop/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.

agentmods 80×15 button for kanban-review-loop

Your own site · 80×15
<a href="https://agentmods.dev/skills/simonblancoe/kanban-mcp/kanban-review-loop"><img src="https://agentmods.dev/badge/skills/simonblancoe/kanban-mcp/kanban-review-loop.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,229 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.01229
Opus 5 $0.00014 $0.00615
Sonnet 5 $0.00005 $0.00246
Haiku 4.5 $0.00003 $0.00123

Measured 9d ago against content hash 9fddb8e5dfc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

kanban-review-loop 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 9d 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.

.claude/skills/kanban-review-loop/SKILL.md · 178 lines

How it starts

The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kanban Review Loop - Continuous Health Monitoring

You are starting the Review Loop - a background daemon that continuously monitors Kanban board health with Ralph Wiggum awareness and session tracking for cross-context-window continuity.

Arguments

  • /kanban-review-loop - Start the daemon
  • /kanban-review-loop stop - Stop (user should kill the background task)

Behavior

This runs as a background process that:

  1. Checks board health every 5 minutes
  2. Monitors escalated tasks (exceeded max iterations)
  3. Detects and reports issues
  4. Auto-spawns QA if review backlog grows
  5. Alerts on stale or blocked tasks
  6. Tracks sprint progress
  7. Generates session summaries for context bridging

Start the Daemon

Run in background using Task tool:

Task tool:
  subagent_type: "general-purpose"
  run_in_background: true
  description: "Kanban review loop daemon"
  prompt: [See daemon instructions below]

Daemon Instructions

You are the KANBAN REVIEW LOOP DAEMON with Ralph Wiggum awareness and session tracking.

## Main Loop (repeat continuously)

### Step 0: Session Check (once at start)
Start session: kanban_session_start with agentId: "review-loop-daemon"
This gives you context about recent activity and any continuity notes.

### Step 1: Board Health Verification
Run: kanban_verify_board_health
This returns structured health status with recommendation.

### Step 2: Full Health Check
Run: kanban_health_check with role: "architect", staleThresholdHours: 24

### Step 3: Check Escalations
Run: kanban_get_escalated_tasks with role: "architect"

### Step 4: Check Active Sprint
Run: kanban_sprint_list with role: "architect"
For each active sprint, check iteration count vs maxIterations.

### Step 5: Analyze & Alert

Check for issues:

**CRITICAL ALERTS:**
- **Escalated tasks** (exceeded maxIterations):
  Log "CRITICAL: Task [title] escalated after [N] iterations - needs human review"
- **Critical tasks not started**:
  Log "ALERT: Critical task [title] waiting"

**WARNING ALERTS:**
- **High iteration tasks** (iteration >= maxIterations - 1):
  Log "WARNING: Task [title] at iteration [N]/[max] - at risk of escalation"
- **Stale tasks** (in_progress > 24h):
  Log "WARNING: Task [title] stale for [hours]h"
- **Sprint at risk** (iteration near max):
  Log "WARNING: Sprint [goal] at iteration [N]/[max]"

**INFO ALERTS:**
- **QA backlog > 3**:
  Log "INFO: QA backlog high, spawning QA agent"
- **Overloaded agents** (> 5 tasks):
  Log "INFO: Agent [id] overloaded with [N] tasks"
- **Low backlog** (< 3 tasks):
  Log "INFO: Backlog low, plan more work"

### Step 6: Auto-Remediation

If QA backlog > 3, spawn QA agent (NOT in background):

Task tool: subagent_type: "general-purpose" prompt: | You are QA. Clear the backlog. 1. kanban_session_start with agentId: "qa-auto" 2. kanban_qa_list with role: "qa" 3. For each task: - kanban_get_task_detail to see iteration history - Review and approve/reject with structured feedback 4. kanban_session_end with summary


### Step 7: Generate Summary
Run: kanban_generate_summary
This updates the session-summary.md file for other agents.

### Step 8: Report Status

Output:
---
[TIME] Review Loop Check #N
Health: [OK | WARNING | CRITICAL]

Sprint Status:
- [Sprint goal]: Iteration [N]/[max] - [status]

Board:
- Backlog: X | In Progress: Y | Blocked: Z | Done: W
- Pending QA: Q
- Escalated: E

Issues:
- [list of alerts]

Actions Taken:
- [any remediation]

Next check in 5 minutes...
---

### Step 9: Sleep
Wait 5 minutes, then repeat from Step 1.

### On Shutdown
When loop is stopped:

kanban_session_end with: agentId: "review-loop-daemon" sessionNotes: "Review loop stopped. X checks performed." cleanState: true

Read the full file on GitHub · 178 lines

Changes

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.

  1. 9d ago First seen · 178 lines · 27 tokens per session scan A 9fddb8e5dfc5

Subscribe to this mod's changes

kanban-review-loop is a skill published in the GitHub repository SimonBlancoE/kanban-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 27 tokens to every session and 1,229 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

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…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

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…

Donchitos/Claude-Code-Game-Studios · 77 tokens

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.

Orkas-AI/Orkas · 5 tokens

projects

List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.

me2resh/apexyard · 24 tokens