agentmods.dev

board-resolve

board-resolve is a skill for Claude Code from GhostlyGawd/engineering-board. It costs 33 tokens per session (2,015 once invoked), scanned A, original, MIT.

A procedure for closing an engineering-board entry after its completion requirements and evidence have been checked. It handles different entry types, including questions, in a fixed order.

In plain words
What is it for?
Use it to resolve completed bugs, tasks, observations, or questions, append findings, rebuild the board, record outcomes, and identify the next ready item.
Why use it?
It prevents entries from being marked resolved before the required evidence is recorded and verification is complete. It also preserves the board and release tracking steps that follow resolution.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Codex.

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

not rated 0 5d ago A scan 33 tokens original MIT
View the source file 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.

agentmods
npx agentmods add skills/ghostlygawd/engineering-board/board-resolve
Any agent
npx skills add GhostlyGawd/engineering-board --skill board-resolve
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, 1 plugin.

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-resolve

README.md
[![agentmods](https://agentmods.dev/badge/skills/ghostlygawd/engineering-board/board-resolve.svg)](https://agentmods.dev/skills/ghostlygawd/engineering-board/board-resolve)
Your own site
<a href="https://agentmods.dev/skills/ghostlygawd/engineering-board/board-resolve"><img src="https://agentmods.dev/badge/skills/ghostlygawd/engineering-board/board-resolve.svg" alt="Measured on agentmods" height="20"></a>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,015 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00033 $0.02015
Opus 5 $0.00016 $0.01007
Sonnet 5 $0.00007 $0.00403
Haiku 4.5 $0.00003 $0.00201

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

Security

Grade A, and why

board-resolve 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 5d 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-resolve/SKILL.md · 183 lines

How it starts

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

Board Resolve

The resolution protocol for all entry types. The question-closing sequence below is a 9-step, order-sensitive protocol: do not skip or reorder. its mandatory steps (1, 6, 7, and 8) are specified precisely in that section.

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_get_entry. Verify the completion criteria and required evidence. For a question, append the Finding before a status change.
  3. Call board_update_entry to append evidence and set status: resolved.
  4. Call board_rebuild. Do not edit BOARD.md directly.
  5. If an H### record cites the entry, offer or execute board_outcomes through its preview and apply boundary. Do not infer causal confirmation from a passing test.
  6. Call board_release with the same session ID that acquired the entry.
  7. Call board_status and state the next ready work item.

Use the detailed rules below to preserve the entry-type-specific sequence. Use slash commands and shell operations only as a fallback when the MCP server is not available.

Identify the entry's board first: the board directory is derived from the entry file's path: engineering-board/<project>/ (or docs/boards/<project>/ on the compat path). All BOARD.md index updates and newest-first ARCHIVE.md insertions go to that project's board, not a different one.

Closing a Bug or Feature

Step 1: Verify done-when criteria

Read the entry's ## Done when section. Confirm the stated verification has been performed. If criteria are not met, do not proceed: note what remains.

Step 2: Set resolved

In the entry file:

status: resolved

Step 3: Insert the newest row in ARCHIVE.md

Read the entry's pattern: field. If present, include it in the archive line:

- B### | title | pattern: tag1, tag2 | resolved: YYYY-MM-DD

If no pattern: field, omit it:

- B### | title | resolved: YYYY-MM-DD

Read the full file on GitHub · 183 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. 5d ago First seen · 183 lines · 33 tokens per session scan A 801afcff481a

Subscribe to this mod's changes

board-resolve is a skill published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 2,015 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.

Project management
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens