agentmods.dev

board-triage

board-triage is a skill for Claude Code from GhostlyGawd/engineering-board. It costs 74 tokens per session (1,622 once invoked), scanned A, original, MIT.

A work-prioritisation guide for an engineering board, the list of tasks and findings a development team needs to handle.

In plain words
What is it for?
It helps order open tasks and mark the selected task as being worked on.
Why use it?
It helps decide what to work on next when several items have different priorities, blockers, dependencies, or affected areas.

Skill for Claude Code

Written for Claude Code: SessionStart hook event. Also seen: mentions subagents; mentions Codex.

Part of the engineering-board plugin — 6 skills, 21 commands, 8 agents, 4 hooks, 1 MCP server shipped together

not rated 0repo yesterday A scan 74 tokens original MIT

Good fit It helps order open tasks and mark the selected task as being worked on.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ghostlygawd/engineering-board/board-triage
View source ↗ GhostlyGawd/engineering-board ghostlygawd.github.io
Install

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.

Any agent
npx skills add GhostlyGawd/engineering-board --skill board-triage
Clone the repo
git clone --depth 1 https://github.com/GhostlyGawd/engineering-board

Made for: Claude Code.

Or install engineering-board, the plugin that ships this one along with the rest of its 6 skills, 21 commands, 8 agents, 4 hooks, 1 MCP server.

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 board-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/ghostlygawd/engineering-board/board-triage/github.svg)](https://agentmods.dev/skills/ghostlygawd/engineering-board/board-triage)
Your own site
<a href="https://agentmods.dev/skills/ghostlygawd/engineering-board/board-triage"><img src="https://agentmods.dev/badge/skills/ghostlygawd/engineering-board/board-triage/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 board-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/ghostlygawd/engineering-board/board-triage"><img src="https://agentmods.dev/badge/skills/ghostlygawd/engineering-board/board-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,622 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.00074 $0.01622
Opus 5 $0.00037 $0.00811
Sonnet 5 $0.00015 $0.00324
Haiku 4.5 $0.00007 $0.00162

Measured 8d ago against content hash 5fe45ca25f72, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

board-triage 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 8d 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.

skills/board-triage/SKILL.md · 112 lines

How it starts

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

Board Triage

Derives the recommended work sequence from open board items and the six triage rules. Also governs Starting Work: setting an item in_progress.

Codex and MCP protocol

Use this protocol when the engineering-board MCP server is available:

  1. Resolve the absolute repository root and project name. Pass root in every tool call.
  2. Call board_status and board_list_entries with ready: true.
  3. Call board_context for the current task and candidate entries. Use board_insights when a repeated pattern or graph cluster can change the recommended scope.
  4. Recommend the next entry from priority, blocker, dependency, affected-area, and systemic-pattern evidence. Explain the reason.
  5. When work starts, call board_claim before board_update_entry. Set the entry to in_progress only after the claim succeeds.
  6. Capture new findings with board_capture_finding. Do not expand the claimed entry silently.

Use the detailed rules below to interpret the returned board state. Use shell commands only as a fallback when the MCP server is not available.

Step 0: Identify the project scope

If triage was requested for a specific project, read that project's board at engineering-board/<project>/BOARD.md. If no project was specified, read the resolved BOARD-ROUTER.md (resolution order: engineering-board/BOARD-ROUTER.md to docs/boards/BOARD-ROUTER.md to legacy docs/board/) to list all projects, then ask which to triage or triage all.

Step 1: Read current state

  1. Read the target board's BOARD.md open list.
  2. For each open item: read its entry file to get priority, status, blocked_by, and affects.
  3. Build the live dependency picture: 
    grep -r "blocked_by:" engineering-board/<project>/ --include="*.md" -h | sort | uniq

Step 1b: Auto-resolve terminal pass (run before triage output)

Before applying the triage rules, run the auto-resolve terminal pass: see ../../references/auto-resolve-pass.md.

Read the full file on GitHub · 112 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. 8d ago First seen · 112 lines · 74 tokens per session scan A 5fe45ca25f72

Subscribe to this mod's changes

board-triage is a skill published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed yesterday), licensed MIT. It adds 74 tokens to every session and 1,622 once invoked, about $0.0004 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.

PlanningProject management
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

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.

wshobson/agents · 54 tokens