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 skills add sangrokjung/claude-forge --skill relaygit clone --depth 1 https://github.com/sangrokjung/claude-forgeWrote 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/sangrokjung/claude-forge/relay)<a href="https://agentmods.dev/skills/sangrokjung/claude-forge/relay"><img src="https://agentmods.dev/badge/skills/sangrokjung/claude-forge/relay/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sangrokjung/claude-forge/relay"><img src="https://agentmods.dev/badge/skills/sangrokjung/claude-forge/relay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 65 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00097 | $0.01592 |
| Opus 5 | $0.00048 | $0.00796 |
| Sonnet 5 | $0.00019 | $0.00318 |
| Haiku 4.5 | $0.00010 | $0.00159 |
Grade A, and why
relay 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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
relay — session relay (compact + next-task baton)
Think of a relay race: the runner hands off the baton before stopping. Before context fills up, this skill produces two things: ① a one-line
/compactcommand that compresses everything so far, and ② a handoff document (a "baton") that lets the next session start running immediately on the next task.
When: context is 70%+ used, work is about to be interrupted, or the user asks to "relay / hand off / next session / baton / handoff."
Important (invariant): this skill never runs /compact directly (a skill cannot execute /compact).
It only produces the one-liner the user pastes in.
Let $SKILL be the absolute path of the directory containing this SKILL.md. Scripts live in $SKILL/scripts/.
Flow
0) Parse arguments
From $ARGUMENTS:
- First positional argument = next task (NEXT_TASK).
- Flags:
--new-session(for a brand-new session — instructs the user to paste the whole baton),--no-ask(skip the clarifying question),--quick(skip prose, skeleton only),--copy(opt-in clipboard copy — off by default, see §6).
1) Collect state
Run bash "$SKILL/scripts/relay-collect.sh" → capture one JSON object. (facts about git/plan/session-summary/tasks/artifacts)
This JSON is the source of truth for every "fact." Do not retype it from memory — quote it verbatim.
2) Confirm the next task
If NEXT_TASK is empty and --no-ask was not passed, ask one AskUserQuestion:
"What's the first thing to do next?" — options pulled from plan.next_unchecked / session_summary.next_steps
/ tasks.items in the collect JSON, plus "type it myself." Tag the answer [from-user].
3) Write the /compact one-liner
bash "$SKILL/scripts/relay-build-focus.sh" "<NEXT_TASK>" "<files>" "<decision>"
<files>= key files relevant to the next task (space/comma separated, optional).<decision>= one line capturing a key decision to preserve (optional).
4) Write the skeleton baton immediately (guarantees an artifact even at 95% context)
bash "$SKILL/scripts/relay-write-baton.sh" "<NEXT_TASK>" <path-to-collect.json or -> "<focus line>"
- Save the collect JSON to a file and pass its path, or pipe it via stdin with
-. - This step leaves a valid (skeleton) baton on disk even without prose.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 99 lines · 97 tokens per session scan A 8557308c02cc
relay is a skill published in the GitHub repository sangrokjung/claude-forge (825 stars, last pushed 5d ago), licensed MIT. It adds 97 tokens to every session and 1,592 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-09-03.
Other skills, from other repositories
caveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
stock-analysis-lead
Orchestrate a US-stock investment analysis — classify sector archetype, fetch SEC filings, dispatch a tiered fan-out of six vertical equity-research agents (business model, earnings quality, balance sheet, management, industry, peer comparison) over a validated JSON findings contract, then synthesize a buy/hold/sell…
api-design
REST API contract designer and reviewer. ALWAYS use when designing new endpoints, reviewing existing API contracts, planning API versioning, or standardizing error models. Covers resource modeling (URL/naming), HTTP method semantics, status code selection, error model consistency, pagination/filtering/sorting…
go-dependency-audit
Go dependency audit specialist for CVE scanning (govulncheck), license risk triage, outdated dependency detection, upgrade impact analysis, and supply chain security. ALWAYS use when auditing go.mod dependencies, running govulncheck, checking license compatibility, planning dependency upgrades, or investigating supply…
kafka-event-driven-design
Kafka event-driven architecture designer and reviewer, at the application/client layer. ALWAYS use when designing, reviewing, or troubleshooting how a service produces or consumes Kafka events — topic and partition-key design, producer and consumer client configuration, consumer group topology, event schema definition…