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-migrategit 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-migrate)<a href="https://agentmods.dev/commands/ghostlygawd/engineering-board/board-migrate"><img src="https://agentmods.dev/badge/commands/ghostlygawd/engineering-board/board-migrate.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 | $0.00062 | $0.01365 |
| Opus 5 | $0.00031 | $0.00682 |
| Sonnet 5 | $0.00012 | $0.00273 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
board-migrate 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 3d 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/board-migrate: choose one migration mode
This compatibility command dispatches one of two independent workflows. Select the mode before you resolve targets or run a script. Do not combine mode flags.
Choose a migration mode
Data migration mode
Use --apply, --rollback, or --status to manage the v0.2.x to v0.3.0
board-data migration. This workflow operates on one or more resolved project
board directories and runs hooks/scripts/board-migrate.sh once for each
target.
Folder relocation mode
Use --relocate to move committed board folders from the compatible
docs/boards/ layout to the engineering-board/ default. This workflow
operates at the repository level and runs hooks/scripts/board-relocate.sh
once.
The two workflows share the /board-migrate command name for compatibility.
They do not share execution steps.
Usage:
/board-migrate --apply [project]
/board-migrate --rollback [project]
/board-migrate --status [project]
/board-migrate --relocate [project]
Data migration workflow
Step 1: Validate the data mode
Accept --apply, --rollback, or --status as the first argument. Accept an
optional project name as the second argument. Stop with the usage text if an
argument is invalid.
Step 2: Resolve project board directories
Source hooks/scripts/board-paths.sh and use eb_board_rows. This applies the
current location order: engineering-board/, then docs/boards/, then the
legacy single-board docs/board/ fallback.
- If the user supplied a project, select only its row.
- If the user omitted a project, select every returned row.
- If no row exists, report that there is no board layout and suggest
/board-init <project>for a new board. Then stop.
Step 3: Run the data migration script
For each selected board directory, run:
bash "$CLAUDE_PLUGIN_ROOT/hooks/scripts/board-migrate.sh" <mode> "<absolute-board-dir>"
Use --apply, --rollback, or --status as <mode>. Capture standard output
for each project. If one project fails, capture its standard error and continue
with the other selected projects.
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.
- 3d ago First seen · 153 lines · 62 tokens per session scan A 2d3879ce8543
board-migrate is a command published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 3d ago), licensed MIT. It adds 62 tokens to every session and 1,365 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
project-recap
Generate a visual project recap for context switching.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage
Triage ServiceNow incidents — list open incidents, assess priority, investigate a specific INC, or analyze trends.
session-log
Create or append a session log entry.
my-tasks
Track, prioritize, and execute tasks with goal alignment and due date awareness. Claude doesn't just remind you — it helps get work done.