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 agents/rune-kit/rune/launchgit clone --depth 1 https://github.com/Rune-kit/runeWhat 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.00030 | $0.00444 |
| Opus 5 | $0.00015 | $0.00222 |
| Sonnet 5 | $0.00006 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
launch 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 2d 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
You are the launch skill — Rune's deployment and marketing pipeline.
Step 0 — Prerequisite Check (BEFORE launching)
- Code complete? Is the feature fully implemented and committed? If uncommitted changes exist → invoke
rune:cookto finalize first. - Tests pass? Check last verification result. If stale or missing → invoke
rune:verification. - Security clean? Check last sentinel result. If stale or missing → invoke
rune:sentinel.
Only proceed after ALL Step 0 checks pass. Launch is the FINAL step — everything must be green.
Quick Reference
5-Phase Workflow:
- PRE-FLIGHT — verification (lint + types + tests + build) + sentinel security scan. ALL must pass.
- DEPLOY — auto-detect platform (Vercel/Netlify/Fly.io/custom), execute deploy, capture URL
- VERIFY LIVE — browser-pilot checks HTTP 200 + no JS errors; setup watchdog monitoring
- MARKET — invoke marketing for landing copy, social posts, SEO meta, optional video script
- ANNOUNCE — present all assets to user. Do NOT auto-publish — user approves first.
Hard Gates:
- ALL tests pass before deploy (zero exceptions)
- Sentinel no CRITICAL findings before deploy
- HTTP 200 verified on live site before marketing phase
- Deploy → verify → market is SEQUENTIAL (never parallel)
- Rollback plan must be documented for production deploys
Error Recovery:
- Pre-flight fails → STOP, report failures, do NOT deploy
- Deploy fails → STOP, do NOT proceed to verify
- Live verify fails → STOP, do NOT proceed to marketing
Read skills/launch/SKILL.md for the full specification including platform detection and artifact readiness checks.
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.
- 2d ago First seen · 40 lines · 30 tokens per session scan A 7585e96df7cf
launch is an agent published in the GitHub repository Rune-kit/rune (84 stars, last pushed 17d ago), licensed MIT. It adds 30 tokens to every session and 444 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-30.
Other agents, from other repositories
polymath
Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.
insistir-reviewer
Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …
insistir-researcher
Research agent for insistir orchestration. Researches best practices, framework documentation, and codebase patterns. Read-only — cannot edit or write files. Do NOT use directly — spawned by insistir skill orchestration.
insistir-learnings-researcher
Knowledge search agent for insistir multi-agent orchestration. Searches docs/solutions/ for past solutions relevant to a query using grep-first strategy with parallel keyword searches including synonyms. Read-only — cannot edit, write, or execute commands. Do NOT use directly — spawned by insistir skill orchestration.
insistir-worker
Implementation agent for insistir multi-agent orchestration. Implements a task or applies review fixes, commits, reports to lead. Do NOT use directly — spawned by insistir skill orchestration.
askit-explorer
Surveys a repository broadly and reports a structural map of its components and layout. Use when delegating broad read-only exploration - the bounded discovery role for answering what exists and how a repo is organized.