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 sonichi/sutando --skill relaygit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/relay)<a href="https://agentmods.dev/skills/sonichi/sutando/relay"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/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/sonichi/sutando/relay"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/relay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.01789 |
| Opus 5.5 | $0.00023 | $0.00716 |
| Sonnet 5.5 | $0.00011 | $0.00358 |
| Haiku 4.5 | $0.00006 | $0.00179 |
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 27d 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Relay
Pass the baton to the next Sutando session. Where session-handoff.sh writes structured facts (recent commits, open PRs, pending Qs), /relay writes the narrative continuity — what you were just working on, what should be checked first, what might break and how to detect it.
Usage: /relay (writes a new relay file) or /relay --append (appends to the most recent unprocessed relay file rather than creating a new one).
Why this exists
src/session-handoff.sh pulls together the structured state for the next session — system status, recent commits, open PRs, pending questions, tasks, conversation tail, quota, repo stats — and writes it to session-state.md. But "I was about to land PR #X and Mini's review said Y matters most" isn't captured by git log, gh pr list, or src/pending_questions_reader.py list. The next session reads structured facts but has to RE-INFER the continuity, which costs context and frequently misses the load-bearing decision.
The relay note encodes intent + judgment — the thing only the LLM that lived through the session can write.
Folder layout
Mirrors Sutando's existing tasks/ and results/ convention:
workspace/relay/
├── relay-{YYYYMMDD}T{HHMMSS}Z.md # pending relay notes (drained into session-state.md, then archived)
└── processed/
└── relay-{YYYYMMDD}T{HHMMSS}Z.md # already drained; kept for audit
- File naming:
relay-$(date -u +%Y%m%dT%H%M%SZ).md— UTC ISO basic form, e.g.relay-20260904T030402Z.md. Do not use the epoch form.session-handoff.shdrains withfind ... -name 'relay-*.md' | sort, which is LEXICOGRAPHIC: everyrelay-17…/relay-18…epoch name sorts before everyrelay-2026…ISO name regardless of when it was written, so a single epoch-named note lands out of order among ISO ones. This file documented the epoch form while every note written since 2026-08-30 used ISO; the doc was the stale half. - Multiple files allowed:
/relayalways creates a NEW file by default.--appendappends to the LATEST unprocessedrelay-*.mdinstead of creating a new one. - Consumption:
src/session-handoff.shreads ALL unprocessedrelay-*.mdfiles in sorted order, appends them tosession-state.mdunder## Relay Notes (from prior sessions), thenmvs each one toprocessed/— but only after confirming its### <basename>header landed in the written file, so an interrupt cannot retire an uncaptured note. - Cleanup: kept indefinitely on local disk. Tiny files (~200-500 bytes each); a year of relay notes is < 1 MB. Sync via the workspace-sync engine (
scripts/sync-workspace.sh) for fleet visibility — the legacysync-memory.shflow is deprecated in v0.3.0 and removed in v0.4.0.
What ships with it
1 file 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.
- 27d ago Changed ab89ffc504a2
- 1mo ago Changed · +5 lines f4db4fc76bf1
- 2mo ago First seen · 81 lines · 57 tokens per session scan A fd48ed131c05
relay is a skill published in the GitHub repository sonichi/sutando (401 stars, last pushed today), licensed MIT. It adds 57 tokens to every session and 1,789 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
gmail
Manage Gmail email — drafting, sending, organizing, filters, vacation replies, and inbox analysis.
schedule
Reminders, automations, and recurring page, dashboard, or status monitoring (cron, RRULE, or fire-at).
inbox-management
Ongoing Gmail inbox management via scheduled runs. Archives known noise, flags urgent items, drafts replies in-thread (never auto-sends), and catches stale follow-ups. Empty polls spend no model tokens. Starts in flag-only mode.
inbox-cleanup
Run a high-recall, multi-pass email inbox cleanup. Pattern-based subject queries catch 25x more archivable email than sender scans alone. Includes urgency triage, classification signals, and post-cleanup filter setup.
notifications
Send notifications through the unified notification router.
outlook
Manage Outlook email — drafting, sending, organizing, rules, vacation replies, and inbox analysis.