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.
git clone --depth 1 https://github.com/Rune-kit/runeWrote 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/agents/rune-kit/rune/launch)<a href="https://agentmods.dev/agents/rune-kit/rune/launch"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/launch/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/agents/rune-kit/rune/launch"><img src="https://agentmods.dev/badge/agents/rune-kit/rune/launch.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.00030 | $0.00444 |
| Opus 5.5 | $0.00012 | $0.00178 |
| Sonnet 5.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 1mo 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.
- 1mo ago First seen · 40 lines · 30 tokens per session scan A 7585e96df7cf
launch is an agent published in the GitHub repository Rune-kit/rune (86 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 444 once invoked, about $0.0001 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 agents, from other repositories
systems-admin
Manages servers, networks, and cloud infrastructure. Expert in Linux, Windows Server, and cloud platforms.
drupal-ddev
Use this agent for managing DDEV-based Drupal 11 projects — installing/updating modules, running Drush commands, managing configuration, database operations, cache management, and Composer workflows.
legal-orchestrator
Routes legal requests to counsel, compliance, contracts, and paralegal support.
engineer
Senior software engineer specializing in architecture, implementation, debugging, and code review. Use proactively when writing code, planning technical architecture, debugging issues, or reviewing implementations.
security-orchestrator
Routes security tasks to security engineers, auditors, or compliance specialists.
fullstack-engineer
End-to-end development across frontend and backend. React, Node.js, databases, APIs, deployment.