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.
npx agentmods add commands/ghostlygawd/engineering-board/board-setupgit clone --depth 1 https://github.com/GhostlyGawd/engineering-boardWhat 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 | $0.00054 | $0.00722 |
| Opus 5 | $0.00027 | $0.00361 |
| Sonnet 5 | $0.00011 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
board-setup 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 yesterday.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board-setup: one command from install to a working board
Collapse the install to value path (previously: /board-init + /board-install-permissions + mode-learning) into one idempotent step (eb-self F002). This command composes existing pieces: it introduces no new state.
What to do
Step 1: Infer the project name
Use $1 if given. Otherwise default to the basename of $CLAUDE_PROJECT_DIR, lowercased with any character outside [a-z0-9-] replaced by -. If the sanitized name is empty, ask the user for a project name and stop.
Step 2: Scaffold (or detect an existing board)
Check whether the resolver already finds a board for this project (source hooks/scripts/board-paths.sh. if engineering-board/BOARD-ROUTER.md lists the project, the board exists).
- Board exists: skip scaffolding: say so in the Step 4 summary ("board already set up"). Never re-scaffold or clobber.
- No board: execute the
/board-initprocedure (Readcommands/board-init.mdand follow its Steps 1-7) with the inferred project name and default affects-prefix. Keep its.gitignoreguidance print-only, as that command specifies.
Step 3: Permission self-check (print the paste block only if needed)
Run:
bash "$CLAUDE_PLUGIN_ROOT/hooks/scripts/board-permission-self-check.sh"
- Exit
0(all installed): note "pipeline permissions: installed" for the summary. - Exit
1(some missing): print the missing-rule paste block exactly as/board-install-permissionswould (the self-check output lists the missing patterns), preceded by one line:To let the pipeline run without prompts, paste the block below into a terminal (interactive by design — this command never edits your settings).Note "pipeline permissions: N missing (paste block above)" for the summary.
Do NOT edit any settings file yourself: permission installation is interactive by design.
Step 4: Report (three readiness lines + one optional first-win line)
Print:
Board ready: engineering-board/<project>/ (<scaffolded fresh | already set up>).
Capture is on: findings land in _sessions/ automatically — run /board-promote <project> to preview them, or /pm-start for advanced batch mode.
Pipeline permissions: <installed | N missing — paste block above>.
Try the pattern-intelligence sample: /board-demo
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.
- yesterday First seen · 55 lines · 54 tokens per session scan A 3722298e9021
board-setup is a command published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 722 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.