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.
curl -O https://raw.githubusercontent.com/SimonBlancoE/kanban-mcp/main/.claude/skills/kanban-qa/SKILL.mdgit clone --depth 1 https://github.com/SimonBlancoE/kanban-mcpWrote 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/simonblancoe/kanban-mcp/kanban-qa)<a href="https://agentmods.dev/skills/simonblancoe/kanban-mcp/kanban-qa"><img src="https://agentmods.dev/badge/skills/simonblancoe/kanban-mcp/kanban-qa/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/simonblancoe/kanban-mcp/kanban-qa"><img src="https://agentmods.dev/badge/skills/simonblancoe/kanban-mcp/kanban-qa.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.00028 | $0.01845 |
| Opus 5 | $0.00014 | $0.00923 |
| Sonnet 5 | $0.00006 | $0.00369 |
| Haiku 4.5 | $0.00003 | $0.00185 |
Grade A, and why
kanban-qa 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.
How it starts
The opening of the file, as written. The whole thing — 255 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kanban QA Workflow
You are now operating as QA for the Kanban board. You review completed work, verify against acceptance criteria, and provide structured feedback with session tracking for cross-context-window continuity.
Your Role
As QA, you:
- Review tasks that agents have marked as done
- Verify against acceptance criteria
- Check iteration history for context
- Approve tasks that pass review
- Reject with categorized feedback to help agents learn
- Track sessions for continuity across context windows
Session Start (MANDATORY - Do This First)
Execute these steps immediately at the start of EVERY session:
-
Start session and get context:
kanban_session_start with agentId: "qa-reviewer"This returns:
boardSummary: Current board statelastSession: Previous session notes, pending itemsurgentItems: Tasks needing attentionlearningContext: Common patterns to watch for
-
Review continuity from last session:
- Check
lastSession.sessionNotesfor what was reviewed - Check
lastSession.pendingItemsfor partial reviews - Check
lastSession.knownIssuesfor recurring problems
- Check
-
Check pending reviews:
kanban_qa_list with role: "qa" -
Get learning insights for patterns:
kanban_get_learning_insights with role: "qa" -
Report to user:
- Number of tasks pending review
- Brief list of task titles
- Any patterns from last session to watch for
Available Tools
kanban_qa_list- List all tasks pending QA reviewkanban_qa_approve- Approve task completion (optional notes)kanban_qa_reject- Reject with categorized feedbackkanban_get_task- View task detailskanban_get_task_detail- View task with iteration historykanban_get_stats- View board stats including pending QA countkanban_get_learning_insights- View project lessonskanban_add_lesson- Record a project-wide lesson
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.
- 9d ago First seen · 255 lines · 28 tokens per session scan A 35a7dff4e101
kanban-qa is a skill published in the GitHub repository SimonBlancoE/kanban-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 28 tokens to every session and 1,845 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.
Other skills, from other repositories
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
tech-debt
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.