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 simota/agent-skills --skill launchgit clone --depth 1 https://github.com/simota/agent-skillsWrote 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/simota/agent-skills/launch)<a href="https://agentmods.dev/skills/simota/agent-skills/launch"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/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/skills/simota/agent-skills/launch"><img src="https://agentmods.dev/badge/skills/simota/agent-skills/launch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Prompt Injection · line 6 Hidden instructions were detected in comments or invisible text. These could contain malicious directives. Manual review is recommended.Fix: Audit all comments and invisible characters. Remove any instructions that direct the agent to perform unauthorized actions. Use plain, reviewable content.
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.00040 | $0.05508 |
| Opus 5.5 | $0.00016 | $0.02203 |
| Sonnet 5.5 | $0.00008 | $0.01102 |
| Haiku 4.5 | $0.00004 | $0.00551 |
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.
How it starts
The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch
Methodical release orchestration and read-only delivery reporting from GitHub PR history, from versioning and rollout design through stakeholder communication and post-release learning.
What ships with it
29 files 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.
- _common 10 B
- reference/canary-rollout.md 7.9 KB
- reference/client-report-templates.md 4.2 KB
- reference/delivery-metrics.md 15 KB
- reference/effort-estimation.md 2.7 KB
- reference/engineering-metrics-guardrails.md 5.3 KB
- reference/engineering-report-templates.md 5.2 KB
- reference/feature-flag-pitfalls.md 3.2 KB
- reference/github-pr-collection.md 6.6 KB
- reference/github-report-cache.md 3.3 KB
- reference/github-report-error-handling.md 3.4 KB
- reference/hotfix-workflow.md 5.9 KB
- reference/mobile-release.md 13 KB
- reference/okr-linkage.md 7.0 KB
- reference/patterns.md 2.2 KB
- reference/pr-flow-analysis.md 8.3 KB
- reference/recipes-index.md 2.5 KB
- reference/reference-index.md 3.3 KB
- reference/release-report-writing.md 4.0 KB
- reference/report-pdf-export.md 3.3 KB
- reference/reporting-handoffs.md 2.5 KB
- reference/retrospective-voice.md 2.7 KB
- reference/rollback-anti-patterns.md 5.9 KB
- reference/strategies.md 9.0 KB
- scripts/generate-report.js 13 KB runs code
- scripts/html-to-pdf.sh 6.1 KB runs code
- scripts/puppeteer-pdf.js 3.4 KB runs code
- styles/report-style.css 5.7 KB
- templates/client-report.html 14 KB
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 Changed · +1 lines dc3223ac98c7
- 7d ago Changed · +3 lines d4cfd1a8a6e2
- 12d ago Changed c0848466b0f6
- 1mo ago Changed d635841e4e31
- 1mo ago Changed · -2 lines c9356e760a5a
- 1mo ago First seen · 294 lines · 40 tokens per session scan A 0fd99d8e484d
launch is a skill published in the GitHub repository simota/agent-skills (95 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 5,508 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-09-03.
Other skills, from other repositories
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
aiwg-delivery-pr
AIWG-specific delivery pull request workflow; explicit alias for aiwg-pr, not a generic repository PR guide.
goal-issues-and-release
Clear the open issue backlog and then cut a release, in one autonomous run: use the batch-all-issues skill to resolve every open issue, then the goal-release skill to draft, merge, and see the release through publication. Never asks the user anything — every decision is made autonomously, and blockers are reported at…
jira-release
Assemble a release from a batch of Jira issues — one release branch, pull request, preview and tracking issue per repository — and, when a person says to ship it, merge it and move the cards on. Insert into the prompt of a run started on a batch of issues.
aiwg-pr
AIWG-specific pull request delivery workflow for AIWG product/workspace changes; not the generic repository PR process.
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.