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-initgit 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.00064 | $0.01598 |
| Opus 5 | $0.00032 | $0.00799 |
| Sonnet 5 | $0.00013 | $0.00320 |
| Haiku 4.5 | $0.00006 | $0.00160 |
Grade A, and why
board-init 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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board-init: scaffold a project board
Initialize the engineering-board layout for project: $1
Affects prefix(es): ${2:-$1/} (defaults to <project-name>/ when omitted)
What to do
You are creating the engineering-board/ scaffold this plugin's hooks and skills expect: a visible, committed-by-default top-level directory (the new default since 1.1.0). Be precise about file paths and idempotent: never clobber an existing file.
Backward compatibility. Existing boards under
docs/boards/(and the legacy single-boarddocs/board/) keep resolving with no action: the resolver checksengineering-board/first, thendocs/boards/, thendocs/board/. This command always scaffolds new boards at theengineering-board/default. To move an existing board onto the new path, use/board-migrate --relocate: do not re-scaffold it here.
Step 1 — Validate inputs
- If
$1(project name) is empty, default it to the repository directory's basename (basename of$CLAUDE_PROJECT_DIR), lowercased with any character outside[a-z0-9-]replaced by-: a smart default beats a dead stop. State the inferred name in the Step 7 report. only ask the user and stop if the sanitized basename comes out empty. Project names should be kebab-case (e.g.navigator,retail-workflow). - Confirm you are in the project root: the directory where
engineering-board/should live (typically the repo root, alongside.git/). If the current working directory looks wrong (e.g. a home dir), confirm with the user before creating files. - Check whether
--privateappears in$ARGUMENTS. it is a flag (not the project name or affects-prefix) that changes the.gitignoreguidance in Step 6.
Step 2 — Create or update engineering-board/BOARD-ROUTER.md
If engineering-board/BOARD-ROUTER.md does not exist, create it with this content:
# Board Router
Maps each project to its board directory. The `affects:` prefix on entry frontmatter determines which board the entry belongs to.
| project | path | affects prefix |
|---------|------|----------------|
| $1 | engineering-board/$1 | ${2:-$1/} |
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.
- 2d ago First seen · 131 lines · 64 tokens per session scan A 2f88581a6ec9
board-init is a command published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 1,598 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
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.