Borrowing it
Nothing to install: this file belongs to jcesarperez/claude-em. 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/jcesarperez/claude-em/main/.claude/skills/check-board/SKILL.mdgit clone --depth 1 https://github.com/jcesarperez/claude-emWrote 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/jcesarperez/claude-em/check-board)<a href="https://agentmods.dev/skills/jcesarperez/claude-em/check-board"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/check-board/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/jcesarperez/claude-em/check-board"><img src="https://agentmods.dev/badge/skills/jcesarperez/claude-em/check-board.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.00061 | $0.03109 |
| Opus 5 | $0.00030 | $0.01554 |
| Sonnet 5 | $0.00012 | $0.00622 |
| Haiku 4.5 | $0.00006 | $0.00311 |
Grade A, and why
check-board 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 10d 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.
Tool
Run this script using the Bash tool:
bash .claude/skills/check-board/scripts/fetch_board.sh <BOARD_ID_OR_URL> --json
BOARD_ID_OR_URL: numeric board id (e.g.5289) or full board URL.- The script trims Done to the last 36h. To Do, In Progress and Done<36h all show up in the snapshot.
The script outputs JSON with this structure:
{
"fetched_at": "2026-05-09T12:00:00Z",
"board": {
"id": "5289",
"name": "...",
"type": "kanban",
"project": "OPS",
"columns": [{ "name": "In Progress", "status_ids": ["10001", "10002"] }]
},
"flagged_field_supported": true,
"metrics": {
"total": 0,
"in_progress": 0,
"todo": 0,
"done_last_36h": 0,
"blocked_count": 0,
"blocked": [{ "key": "...", "summary": "...", "status": "...", "statusCategory": "...", "column": "...", "assignee": "Name", "time_in_status": "Xd Yh Zm" }],
"stuck": [{ "key": "...", "summary": "...", "status": "...", "column": "...", "assignee": "Name", "is_blocked": false, "time_in_status": "Xd Yh Zm", "seconds": 0, "severity": "warning|critical" }],
"unassigned_in_progress": [{ "key": "...", "summary": "...", "status": "...", "column": "...", "time_in_status": "..." }],
"regressions_last_7d": [{ "key": "...", "summary": "...", "at": "...", "from": "...", "to": "..." }],
"throughput_7d": 0,
"throughput_14d": 0,
"median_cycle_time_days": 0.0,
"columns": [{ "name": "...", "count": 0, "in_progress_count": 0, "stuck_count": 0 }],
"assignees": [{ "assignee": "Name or null", "count": 0, "keys": ["..."], "max_time_in_status_seconds": 0, "stuck_count": 0, "blocked_count": 0 }],
"idle_assignees": ["Name"],
"bugs_at_risk": [{ "key": "...", "summary": "...", "status": "...", "column": "...", "assignee": "Name", "priority": "High", "duedate": "YYYY-MM-DD or null", "days_until_due": 0, "risk": "red|yellow", "reason": "due date|Highest priority, no due date" }],
"bugs_other_count": 0,
"epics": [{ "key": "EPIC-1", "summary": "...", "status": "...", "active_count": 0, "in_progress_count": 0, "stuck_count": 0, "blocked_count": 0, "red_bug_count": 0, "yellow_bug_count": 0, "issue_keys": ["..."] }],
"issues_without_epic": 0
},
"issues": [/* full snapshot, same per-issue shape as inside metrics + changelog-derived fields */]
}
What ships with it
1 file 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.
- 10d ago First seen · 255 lines · 61 tokens per session scan A f3fd1f249273
check-board is a skill published in the GitHub repository jcesarperez/claude-em (95 stars, last pushed 2mo ago), licensed MIT. It adds 61 tokens to every session and 3,109 once invoked, about $0.0003 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-30.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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…
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.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.