Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add GhostlyGawd/engineering-board/plugin install engineering-boardWrote 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/ghostlygawd/engineering-board/board-claim-release)<a href="https://agentmods.dev/commands/ghostlygawd/engineering-board/board-claim-release"><img src="https://agentmods.dev/badge/commands/ghostlygawd/engineering-board/board-claim-release.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.00065 | $0.00901 |
| Opus 5 | $0.00032 | $0.00451 |
| Sonnet 5 | $0.00013 | $0.00180 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
board-claim-release 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board-claim-release: manual claim release
Release a stuck or orphaned claim so another worker (or the same user) can re-acquire it. The Stop hook's worker-mode procedure releases claims automatically each turn. this command is the manual fallback for when a worker session has gone offline or a claim is visibly stuck.
What to do
Step 1: Parse arguments
Extract <entry-id> from $ARGUMENTS. The entry-id must match ^[A-Z][0-9]+$ (e.g. B017, F003, Q012).
Also check whether --force appears in $ARGUMENTS.
If no entry-id is found or the pattern does not match, print:
Usage: /board-claim-release <entry-id> (e.g. B017). No action taken.
Then stop.
Step 2: Resolve board directory
Resolve the board router in this order (first hit wins), then extract the board path for the current project:
${CLAUDE_PROJECT_DIR}/engineering-board/BOARD-ROUTER.md: default since 1.1.0${CLAUDE_PROJECT_DIR}/docs/boards/BOARD-ROUTER.md: compat (pre-1.1.0)${CLAUDE_PROJECT_DIR}/docs/board/: legacy single-board (no router)
Step 3: Check claim existence
Check whether <board-dir>/_claims/<entry-id>/ exists.
If not, print:
No claim found for <entry-id>. Nothing to release.
Then stop.
Step 4: Read claim owner and current session
Read <board-dir>/_claims/<entry-id>/owner.txt. Extract the session_id: line value (second whitespace-separated token).
Read ${CLAUDE_PROJECT_DIR}/.engineering-board/last-stop-stdin.json if it exists. Extract the session_id field. If the file does not exist or has no session_id, use an empty string "" as the current session_id.
Step 5: Run the release script
Run:
bash $CLAUDE_PLUGIN_ROOT/hooks/scripts/board-claim-release.sh <board-dir> <entry-id> <session-id>
Where <session-id> is:
- Without
--force: the current session_id from Step 4. - With
--force: the owner session_id read fromowner.txtin Step 4 (so the script's owner-check passes regardless of who is calling).
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 · 87 lines · 65 tokens per session scan A 56957ff1e4ac
board-claim-release is a command published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 7d ago), licensed MIT. It adds 65 tokens to every session and 901 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-31.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
sync-linear
Sync current work with Linear ticket status.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
dispatcher
Pick the next-best repo to work on across the portfolio — rank free repos, recommend one, claim its lease atomically, and route to the entry command.
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.