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/GhostlyGawd/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-rebuild)<a href="https://agentmods.dev/commands/ghostlygawd/engineering-board/board-rebuild"><img src="https://agentmods.dev/badge/commands/ghostlygawd/engineering-board/board-rebuild.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.00061 | $0.01703 |
| Opus 5 | $0.00030 | $0.00851 |
| Sonnet 5 | $0.00012 | $0.00341 |
| Haiku 4.5 | $0.00006 | $0.00170 |
Grade A, and why
board-rebuild 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 7d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board-rebuild: regenerate BOARD.md and GRAPH.yml from the filesystem
The deterministic-cache refresh command. Treats the entry .md files in bugs/, features/, questions/, observations/ as the single source of truth and regenerates both BOARD.md (the index) and GRAPH.yml (the structural graph) from them. This is the fix for B004 (board state drifts from filesystem).
Safe to run anytime. Both outputs are deterministic: same input always produces byte-identical output (modulo generated_at in GRAPH.yml). No LLM calls in the regeneration step.
Other modifying commands should call this as their last step (intake, resolve, manual entry edits). That closes the staleness loop entirely.
Trigger
/board-rebuild: rebuild every project in BOARD-ROUTER.md/board-rebuild <project-name>: rebuild just that project
Process
Step 1 — Resolve target board(s)
Resolve the board router in this order (first hit wins): $CLAUDE_PROJECT_DIR/engineering-board/BOARD-ROUTER.md (default since 1.1.0), then $CLAUDE_PROJECT_DIR/docs/boards/BOARD-ROUTER.md (compat). Target either the named project or all listed. Fall back to legacy docs/board/ if no router.
Step 2 — Scan entry files
For each project's board directory, list *.md files under bugs/, features/, questions/, observations/. Parse YAML frontmatter from each: id, type, priority, status, title, pattern, tags, blocked_by.
Step 3 — Validate
Report (do not auto-fix) any of:
- Duplicate IDs: same
id:field across two or more files. Indicates parallel-write corruption (B005). - Resolved entries still listed in BOARD.md: entry has
status: resolvedbut appears in current BOARD.md's Open section. Will be removed in this rebuild. - Orphan resolved entries: entry has
status: resolvedbut not in ARCHIVE.md. Should be archived manually or via/board-resolve. Do not auto-archive (resolutions need provenance). - Missing required frontmatter:
id,type,title,discoveredmissing. Report path for manual fix. - Dangling
blocked_by:references:blocked_by:lists a Q### that does not exist or is resolved. Report.
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.
- 7d ago First seen · 120 lines · 61 tokens per session scan A e6dab84fb210
board-rebuild is a command published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 1,703 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.