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/assemblyai/blurt/launch-metricsnpx skills add AssemblyAI/blurt --skill launch-metricsgit clone --depth 1 https://github.com/AssemblyAI/blurtWrote 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/assemblyai/blurt/launch-metrics)<a href="https://agentmods.dev/skills/assemblyai/blurt/launch-metrics"><img src="https://agentmods.dev/badge/skills/assemblyai/blurt/launch-metrics.svg" alt="Measured on agentmods" 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 | $0.00059 | $0.00403 |
| Opus 5 | $0.00030 | $0.00201 |
| Sonnet 5 | $0.00012 | $0.00081 |
| Haiku 4.5 | $0.00006 | $0.00040 |
Grade A, and why
launch-metrics 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 4d 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
Blurt launch metrics
A $0 measurement backbone from the GitHub API (campaign §7). No analytics
vendor required — gh is the whole toolchain.
What it reports
- Blurt.dmg downloads — the primary KPI. Summed
download_countacross releases'Blurt.dmgassets. Bands (4-week, campaign §1): baseline ~500, good ~1,500, great 4,000+. - GitHub stars — bands: baseline +100, good +300, great +800.
- Unique visitors & referrers — uniques are the source of truth (raw view
counts are inflated by bots and your own reloads, so the script reports unique
visitors and ranks referrers by uniques). Needs push access; the
repos/.../traffic/*endpoints are owner-only. Watch for awesome-list and dev-site referrers as the evergreen layer kicks in (§7).
Run it
.claude/skills/launch-metrics/metrics.sh
Requires gh auth status to be logged in. The script is read-only.
Recurring during launch week
Wrap with the built-in loop for the §7 daily cadence:
/loop 1d /launch-metrics
Then drop to a weekly check for the rest of the month. Note the script gives a point-in-time download total; track the day-over-day delta yourself (or paste the prior day's number) to see the rate, which is what the bands are really about.
What ships with it
1 file 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.
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.
- 4d ago First seen · 42 lines · 59 tokens per session scan A af740f6e6381
launch-metrics is a skill published in the GitHub repository AssemblyAI/blurt (5 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 403 once invoked, about $0.0003 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-31.
Other skills, from other repositories
scarf-template-author
Scaffold a new Scarf project OR enrich an existing one after a Scarf "Upgrade Project" — dashboard, optional configuration schema, optional cron job, AGENTS.md, and (via the scarf-miniapp-author skill) a starter mini-app — from a short conversational interview. Output is immediately usable locally and cleanly…
scarf-miniapp-author
Author a Scarf mini-app — a small sandboxed web surface (HTML/CSS/JS) that renders inside a project's cockpit and talks to the bound Hermes session + project data through the versioned window.scarf bridge. Use to build a bespoke panel (a task board, an approval queue, a chart, a data table) for a project.
awesome-swift-macos-apps-docs
Use when adding, updating, or validating app entries in the awesome-swift-macos-apps repository, especially when maintaining both README.md and README.zh.md with concise one-sentence descriptions, correct category placement, and consistent bilingual formatting.
release
发布 Usage4Claude 新版本时使用。当用户说“发布新版本 / 发版 / 出新版 / release / 打 tag 发布 / 准备发版材料”等，用本 skill 引导完成从收集变更、编写 CHANGELOG 与 RELEASENOTES、更新版本号、编译验证，到发版 commit、CI 自动发布的完整流程。.
repo-build-pr
End-to-end implementation loop for the os-clovy repo: study the prompt, ask the clarifying questions that change what gets built, plan and architect on the session model while delegating bulk implementation and review to cheaper strong models, isolate work in git worktrees, validate with deterministic checks plus…
macos-harness
Control a whole Mac from one persistent Python session with screenshots, PID-targeted input, an animated virtual pointer, targeted Apple Accessibility, Apple Events, Browser Harness CDP, and filesystem access. Use for native, Electron, browser, dialog, file, or cross-app tasks without moving the physical cursor or…