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 spacegrowth/claude-relay/plugin install relayWrote 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/skills/spacegrowth/claude-relay/board)<a href="https://agentmods.dev/skills/spacegrowth/claude-relay/board"><img src="https://agentmods.dev/badge/skills/spacegrowth/claude-relay/board.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.00096 | $0.00449 |
| Opus 5 | $0.00048 | $0.00225 |
| Sonnet 5 | $0.00019 | $0.00090 |
| Haiku 4.5 | $0.00010 | $0.00045 |
Grade A, and why
board 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 8d 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.
What it actually says
Run: ${CLAUDE_PLUGIN_ROOT}/bin/relay board --open
(Call relay via ${CLAUDE_PLUGIN_ROOT}/bin/relay — Claude Code substitutes the plugin's absolute
path — not bare relay, which often isn't on the Bash tool's non-interactive PATH.)
This writes ~/.relay-tasks/board.html (override with --out PATH) and opens it. It is a
static snapshot built from exactly the data relay list/check use (liveness is refreshed
and finished executors are auto-closed on the way, same as list), so it never disagrees with
the table — re-run to refresh. Light theme by default; the ☀️/🌙 button switches and remembers.
On the page: a summary strip (leads / live executors / busy / reported / closed), warning banners
(orphans, reports not yet delivered to their lead, heavy sessions, stale wake hooks), then one
card per lead with its executors. Click an executor row to expand its packet timeline — each
packet's gist, the report's outcome sentence and TL;DR (Status · Risk · UNVERIFIED), and links to
the packet, report and diff page — plus copyable relay … commands. The filter box narrows
executors by name/topic/status/model/worktree; "show closed" reveals parked sessions.
Pass --lead "${CLAUDE_CODE_SESSION_ID}" to scope executors to this lead's (plus unowned ones);
--json emits the board data instead of HTML for programmatic use.
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.
- 8d ago First seen · 30 lines · 96 tokens per session scan A b46b3a487d7a
board is a skill published in the GitHub repository spacegrowth/claude-relay (1 stars, last pushed yesterday), licensed MIT. It adds 96 tokens to every session and 449 once invoked, about $0.0005 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 skills, from other repositories
dispatch
Use when a task file exists in .hyperflow/tasks/ and workers need dispatching. Fans out parallel workers under per-batch Reviewers, runs a final integration review, and commits per sub-task. Endpoint of the auto-chain — no auto-deploy. Trigger with /hyperflow:dispatch, "run the plan", "execute the task", "build it"…
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
opportunity-solution-tree
Build an Opportunity Solution Tree (OST) to structure product discovery — map a desired outcome to customer opportunities, possible solutions, and experiments. Based on Teresa Torres' Continuous Discovery Habits. Use when the team is unclear what to build next, when multiple opportunities compete, or before writing a…
done-blocked
Reusable reporting contract for any agent that hands work back to the pipeline. Forces ONE of two terminal statuses (DONE or BLOCKED) with a specific evidence shape. Stops vague "probably finished" and "kind of stuck" verdicts.
pm-planning
Decomposition methodology for pm agent — turns an approved ARCH document into a Beads task list with explicit dependencies, time-boxes, and acceptance criteria. The pipeline can only orchestrate work it can see; this skill defines what "seeable work" looks like.
vertical-construction
Domain knowledge for the construction vertical (contractors, field crews) so architect and pm don't spec construction products naively. Covers the vocabulary (bid vs estimate, takeoff, retainage, change order, AIA G702/G703, lien waiver, draw schedule), the non-obvious money rules that incumbents like Procore price…