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 slaveOftime/open-relay --skill oly-subagentgit clone --depth 1 https://github.com/slaveOftime/open-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/slaveoftime/open-relay/oly-subagent)<a href="https://agentmods.dev/skills/slaveoftime/open-relay/oly-subagent"><img src="https://agentmods.dev/badge/skills/slaveoftime/open-relay/oly-subagent/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/slaveoftime/open-relay/oly-subagent"><img src="https://agentmods.dev/badge/skills/slaveoftime/open-relay/oly-subagent.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.02001 |
| Opus 5.5 | $0.00020 | $0.00800 |
| Sonnet 5.5 | $0.00010 | $0.00400 |
| Haiku 4.5 | $0.00005 | $0.00200 |
Grade A, and why
oly-subagent 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 today.
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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Orchestrate and supervise sub-agents with oly
oly skill --subagent prints this self-contained guide directly from the oly binary (no local file read, oly skill, or oly start --help is needed for standard workflows).
Use oly as a durable PTY and supervision runtime for user-authorized agent CLIs (pi, codex, claude, etc.). This skill does not authorize delegation, extra agents, approval bypass, or edits outside the user's scope. Use the agent CLI and model already chosen by the user or environment.
Core oly CLI reference:
oly daemon status— check daemon health (oly daemon start --detachonly if confirmed stopped; never stop/restart a shared daemon).oly start --detach --disable-notifications --title "<name>" --cwd <dir> [--tag <t>] [--node <n>] <cmd> [args...]— launch worker and print<ID>(olyflags go before<cmd>).oly logs <ID> --tail <N> --wait <exit|prompt|output|idle|match> --timeout <dur>— wait for gate (0met,2timeout,1error), then print output.oly info <ID> --json— inspectstatus,exit_code,input_needed, andprogram_status.
1) Right-size the topology (lower defaults first)
Multi-agent flows consume more tokens than single-agent work. Choose the smallest topology that fits the task:
| Topology | When to use | How to run |
|---|---|---|
| Direct (0 workers) | Small, immediate, or tightly coupled edits where you would just sit waiting on a single worker. | Do the work directly in your own session. |
| Single worker (1) | Offload a noisy investigation, test/build diagnosis, or isolated module change to keep raw logs out of your context. | Spawn 1 worker, wait for completion, verify its output artifact. |
| Fan-out / Map-Reduce | $N$ independent modules, files, or hypotheses with disjoint write scopes. | Map: launch $N$ workers in one shell call; each writes a compact result/file. Reduce: wait for all in one shell loop, then synthesize/verify. |
| Staged pipeline | Sequential phases with hard gates (Scan -> Implement -> Review/Test). |
Run Phase 1 workers to produce a compact plan/diff; gate Phase 2 on verified Phase 1 output. |
| Hierarchical (Lieutenants) | Large multi-subsystem work where flat fan-out would bottleneck the lead agent. | Delegate each subsystem to a lieutenant worker that coordinates its own sub-workers and returns one verified summary. |
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.
- today Changed · +20 lines 8b600742e37c
- 3d ago First seen · 72 lines · 49 tokens per session scan A ea8139eb8fb3
oly-subagent is a skill published in the GitHub repository slaveOftime/open-relay (95 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 2,001 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-10-14.
Other skills, from other repositories
tui-explorer
Discover and replay terminal UI paths using agent-tui. Use when you need to launch a TUI app, explore navigation with bounded BFS, generate markdown acceptance tests, and verify those tests repeatedly. Do not use for web or desktop GUI automation.
agent-tui
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo…
contributor-onboarding
Help a new contributor get productive on this checkout - inspect sync state against main, build, run the repository's exact verification gate, and produce a local what's-new digest. Never fetches, pulls, or modifies a dirty tree on its own. Explicit-only.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.