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 agentmods add skills/slaveoftime/open-relay/oly-appsnpx skills add slaveOftime/open-relay --skill oly-appsgit clone --depth 1 https://github.com/slaveOftime/open-relayWhat 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 | $0.00021 | $0.00469 |
| Opus 5 | $0.00010 | $0.00234 |
| Sonnet 5 | $0.00004 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
Grade A, and why
oly-apps 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 3d 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
Overview
Publish rich output as a web app served by the oly daemon. Each app lives in its own folder under <OLY-ROOT>/wwwroot/apps/ and is reachable at:
http://127.0.0.1:<OLY-PORT>/apps/<app-name>/
Run oly daemon status to discover <OLY-PORT> and <OLY-ROOT>.
Quick start
Simple HTML app
Drop an index.html (plus any assets) into a new folder:
<OLY-ROOT>/wwwroot/apps/<app-name>/index.html
No manifest needed — oly discovers index.html automatically.
SPA or proxied service
Create oly.app.json in the app folder:
{
"title": "My App",
"entry": "index.html",
"redirect_files": ["../shared-assets"]
}
Set the base href to ./ (or /apps/<app-name>/) so relative asset paths resolve correctly when served from the discovered route.
Manifest schema (oly.app.json)
| Field | Type | Description |
|---|---|---|
title |
string? |
Display name. |
description |
string? |
Short description. |
icon_href |
string? |
Icon URL or relative path. |
app_type |
string? |
App type hint. |
redirect_files |
string[] |
Extra asset directories outside the app folder. Oly checks the app folder first, then each redirect directory in order; 404 if not found. |
entry |
string |
Required. URL, path, or HTML file to serve as the entry point. |
Rules
- Use relative asset paths or the
/apps/<app-name>/base — absolute paths will break. - One folder per app, one
index.htmlor oneoly.app.jsonper folder. - Use
redirect_filesto share static assets across apps without copying.
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.
- 3d ago First seen · 59 lines · 21 tokens per session scan A 2243aee3b71f
oly-apps is a skill published in the GitHub repository slaveOftime/open-relay (93 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 469 once invoked, about $0.0001 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-30.
Other skills, from other repositories
testing-api-authentication-weaknesses
Tests API authentication mechanisms for weaknesses including broken token validation, missing authentication on endpoints, weak password policies, credential stuffing susceptibility, token leakage in URLs or logs, and session management flaws. The tester evaluates JWT implementation, API key handling, OAuth flows, and…
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
start
Session initialization and lifecycle management: bootstraps session context, organizes files, generates CLAUDE.md, manages soul purpose lifecycle with completion protocol and active context harvesting. Use when user says /start, /init, bootstrap session, initialize session, or organize project.
s-continue
Cheaper and faster than /compact. Restores previous session context from Claude Code AND Codex transcripts by reading them directly — no LLM calls, no token cost. Also auto-loads a handoff written by /s-compact, if one exists. Triggers on "s-continue", "restore context", "what was I doing", "pick up where I left off"…
test-spec-gen
Universal test specification generator that explores codebases, researches best practices, and generates comprehensive test specs via multi-agent orchestration. Outputs Hermes-style test specification documents with TC-XXX formatting, area segmentation, and optional Trello card conversion.
start
Session initialization and lifecycle management: bootstraps session context, organizes files, generates CLAUDE.md, manages soul purpose lifecycle with completion protocol and active context harvesting. Use when user says /start, /init, bootstrap session, initialize session, or organize project.