Borrowing it
Nothing to install: this file belongs to theshadow27/mcp-cli. 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/theshadow27/mcp-cli/main/.claude/skills/board-overview/SKILL.mdgit clone --depth 1 https://github.com/theshadow27/mcp-cliWrote 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/theshadow27/mcp-cli/board-overview)<a href="https://agentmods.dev/skills/theshadow27/mcp-cli/board-overview"><img src="https://agentmods.dev/badge/skills/theshadow27/mcp-cli/board-overview.svg" alt="Measured on agentmods" 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.00044 | $0.00770 |
| Opus 5 | $0.00022 | $0.00385 |
| Sonnet 5 | $0.00009 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
board-overview 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 6d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Board Overview
Analyze the open issue board, identify themes and arcs, and write a sprint file the orchestrator can use for strategic planning.
Step 1: Read the Board
Fetch all open issues:
gh issue list --state open --json number,title,labels,body --limit 200
Also fetch recently closed issues (last 2 weeks) for completed-arc detection:
gh issue list --state closed --json number,title,labels,closedAt --limit 50
Step 2: Identify Arcs
Group issues into thematic arcs based on:
- Feature area: which package or subsystem they touch (daemon, CLI, control, core, auth, config, testing, docs, orchestration/skills)
- Dependency chains: issues that must be done in sequence (look for "Related", "Depends on", "Blocks" in bodies)
- Natural work sequences: issues that share context and are more efficient to do together
An arc is a cluster of 2+ related issues. Standalone issues that don't fit an arc go under "Ungrouped".
Step 3: Assess Each Arc
For each arc, determine:
- Status: active (has open issues), completed (all issues closed recently), stalled (open issues but no recent activity)
- Ready issues: which issues in the arc can be picked up now (no unresolved dependencies, no
needs-clarificationlabel) - Blocked issues: which are waiting on other issues or human input
- Suggested ordering: dependency-respecting sequence for implementation
Step 4: Write the Sprint File
Write or update .claude/arcs.md with the following structure:
# Board Overview
> Auto-generated by /board-overview on YYYY-MM-DD. Do not edit manually.
## Active Arcs
### Arc Name
_N open issues, M ready_
| # | Title | Status | Dependencies |
|---|-------|--------|--------------|
| 123 | Issue title | ready | — |
| 124 | Another issue | blocked | #123 |
### Another Arc
...
## Ungrouped Issues
| # | Title | Labels |
|---|-------|--------|
| 200 | Standalone issue | bug |
## Recently Completed Arcs
### Arc Name (completed YYYY-MM-DD)
- #100 Issue title
- #101 Another issue
## Summary
- **Total open**: N issues
- **Ready to pick up**: M issues
- **Blocked**: K issues
- **Active arcs**: L
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.
- 6d ago First seen · 101 lines · 44 tokens per session scan A 8ebd8701e40e
board-overview is a skill published in the GitHub repository theshadow27/mcp-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 44 tokens to every session and 770 once invoked, about $0.0002 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
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…
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.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.