Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/ruslan-korneev/claude-pluginsWrote 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/commands/ruslan-korneev/claude-plugins/board)<a href="https://agentmods.dev/commands/ruslan-korneev/claude-plugins/board"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/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/commands/ruslan-korneev/claude-plugins/board"><img src="https://agentmods.dev/badge/commands/ruslan-korneev/claude-plugins/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.00012 | $0.00734 |
| Opus 5.5 | $0.00005 | $0.00294 |
| Sonnet 5.5 | $0.00002 | $0.00147 |
| Haiku 4.5 | $0.00001 | $0.00073 |
Grade A, and why
linear: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 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Command /linear:board
Display a kanban board view grouped by workflow state.
Instructions
Step 0: Validate Configuration
Check LINEAR_API_KEY and LINEAR_TEAM are set.
Step 1: Fetch Workflow States
Use workflowStates query to get all states for the team. Sort by type order: backlog → unstarted → started → completed. Exclude triage and canceled from board display.
Step 2: Fetch Issues
Build filter:
- Team:
$LINEAR_TEAM - Project: argument or
basename $(pwd) - Assignee: if provided
- Cycle: if provided, resolve "current" to active cycle
- Exclude archived issues
Use issues query with filter.
Step 3: Group by State
Group fetched issues by their state into columns.
Step 4: Render Board
Display as ASCII kanban board:
## Board: backend-api (Sprint 42)
| Backlog (3) | Todo (2) | In Progress (4) | In Review (1) | Done (8) |
|-------------|----------|------------------|---------------|----------|
| TEAM-130 | TEAM-128 | TEAM-123 | TEAM-127 | TEAM-110 |
| Fix cache | Add logs | Auth flow | API tests | Setup CI |
| P:Med 2pts | P:Low 1p | P:Urg 5pts J.D. | P:Hi 3pts J.S | P:Med 2p |
| | | | | |
| TEAM-131 | TEAM-129 | TEAM-124 | | TEAM-111 |
| Update deps | Refactor | Pagination | | Add CORS |
| P:Low 1pt | P:Med 2p | P:Hi 3pts J.S. | | P:Low 1p |
| | | | | |
| TEAM-132 | | TEAM-125 | | ...+6 |
| Add metrics | | User roles | | |
| P:Low 1pt | | P:Med 2pts | | |
Formatting rules:
- Each card shows: identifier, title (truncated to column width), priority + estimate + assignee initials
- Column header includes state name and issue count
- Max 5 cards per column, then show "+N more"
- Skip empty columns unless they are "started" type (always show In Progress)
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 · 86 lines · 12 tokens per session scan A fcf6273a5b04
linear:board is a command published in the GitHub repository ruslan-korneev/claude-plugins (5 stars, last pushed 7mo ago), licensed MIT. It adds 12 tokens to every session and 734 once invoked, about $0.0000 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-31.
Other commands, from other repositories
spec
A requirements-planning command for OpenSpec, a tool that records software changes as proposals, specification updates, and task lists. It clarifies the request, challenges risky assumptions, and pauses for approval before implementation.
octo-schedule
Manage scheduled workflow jobs for the Claude Octopus scheduler.
octo-scheduler
Manage the Claude Octopus scheduled workflow runner daemon.
next
Read the active sprint’s current status. Refresh stale compilation using grainulator compile --dir or grainulator.compile. Use the resulting nextactions with the user’s current scope and authorization. Output only the two Auto and Manual lists below, with no recap, status counters or offer to continue. Continue useful…
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.