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/check)<a href="https://agentmods.dev/skills/spacegrowth/claude-relay/check"><img src="https://agentmods.dev/badge/skills/spacegrowth/claude-relay/check.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.00045 | $0.00393 |
| Opus 5 | $0.00023 | $0.00197 |
| Sonnet 5 | $0.00009 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
check 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.
What it actually says
Call relay as ${CLAUDE_PLUGIN_ROOT}/bin/relay (Claude Code substitutes the plugin's absolute path
when this skill loads) — not bare relay, which often isn't on the Bash tool's non-interactive PATH.
If $session_id is given, run: ${CLAUDE_PLUGIN_ROOT}/bin/relay check $session_id
Otherwise run: ${CLAUDE_PLUGIN_ROOT}/bin/relay check --all
Liveness is judged by the executor's recorded process id, not its tab title — Claude Code
mutates its own iTerm tab title while working, so a title change never by itself means the executor
died. Status flips: busy → reported once the report file exists (a report means done,
regardless of process/tab state); → stalled if the process died with no report but the tab's
still open, or it's been busy far longer than expected; → dead only when the process is gone AND
the tab has closed. A stalled session needs you to look at that tab directly — relay check only
detects it, it doesn't fix it.
check also runs the auto-close sweep on the session(s) it checks: a finished executor whose
report you've already seen gets parked once its work has landed (claimed files clean in the
worktree) or it has idled past auto_close_idle_minutes — printed as a 🛏 line. Nothing is lost;
/relay:send resumes it. Pin with relay keep <sid> if a follow-up is imminent.
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 · 28 lines · 45 tokens per session scan A a4432a7c7991
check is a skill published in the GitHub repository spacegrowth/claude-relay (1 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 393 once invoked, about $0.0002 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
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.
dagr-producer
Emit and maintain a dagr run file — a live, contract-valid JSON description of recursive projects, tasks, attempts, gates, evidence, policies, events, and operator-message resolutions that dagr view renders as a DAG. Use when orchestrating agents or tracking multi-step work that a dagr pane should display.
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…