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-graph)<a href="https://agentmods.dev/commands/ghostlygawd/engineering-board/board-graph"><img src="https://agentmods.dev/badge/commands/ghostlygawd/engineering-board/board-graph.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.00054 | $0.01739 |
| Opus 5 | $0.00027 | $0.00870 |
| Sonnet 5 | $0.00011 | $0.00348 |
| Haiku 4.5 | $0.00005 | $0.00174 |
Grade A, and why
board-graph 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board-graph: build a deterministic structural graph of the live board
Generates engineering-board/<project>/GRAPH.yml: a purely deterministic
machine-readable graph of all open entries and canonical pattern records. Same
canonical Markdown produces the same structural facts. No LLM runs in the
construction step.
Downstream AI consumers read the structural facts and interpret them in their own context: interpretation happens at point of use, not at graph-build time.
Trigger
/board-graph: graph every project in BOARD-ROUTER.md (one GRAPH.yml per project)/board-graph <project-name>: graph just that project/board-graph <project-name> --full: bypass the disposable incremental cache
Output schema
JSON-compatible YAML with these top-level keys:
schema_versiongenerated_atsource_fingerprintbuild_modeprojectentries_analyzednodesedgestopologyunresolved_patternsfindingsread_order,drill_in
Use entry IDs (B003, O002, F001) everywhere: never titles.
Edge kinds: all deterministic
| kind | weight | source | LLM? |
|---|---|---|---|
blocked-by |
3 | frontmatter blocked_by: |
no |
superseded-by |
3 | frontmatter superseded_by: |
no |
merged-into |
3 | frontmatter merged_into: |
no |
contradicts |
3 | frontmatter contradicts: |
no |
shared-pattern |
2 | same resolved pattern_ids: identity, with legacy label fallback |
no |
shared-affects-prefix |
2 | overlapping non-null affects: prefix |
no |
shared-tag |
1 | same non-universal tag: (skip tags on >50% of entries) |
no |
No shared-topic, no claim-vs-bug edges. If the user wants a semantic connection captured, they add it as either an explicit frontmatter relationship (contradicts: [F001]) or a tag/pattern.
Deduplication: for the same {from, to} pair, keep the highest-weight edge per kind. emit multiple edges only if kind differs. If two edges of the same kind would be added (e.g. two shared patterns), keep one and concatenate values: value: "hygiene, entry-lifecycle".
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 · 167 lines · 0 tokens per session scan A 737411187afa
board-graph is a command published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 6d ago), licensed MIT. It adds 54 tokens to every session and 1,739 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.