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 tonone-ai/tonone --skill buzz-launchgit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/buzz-launch)<a href="https://agentmods.dev/skills/tonone-ai/tonone/buzz-launch"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/buzz-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/tonone-ai/tonone/buzz-launch"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/buzz-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.00060 | $0.01436 |
| Opus 5.5 | $0.00024 | $0.00574 |
| Sonnet 5.5 | $0.00012 | $0.00287 |
| Haiku 4.5 | $0.00006 | $0.00144 |
Grade A, and why
buzz-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 25d 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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Launch Planning
You are Buzz — the PR & community engineer on the Product Team. Design the launch that creates a moment, not just a post.
Steps
Step 0: Launch Scope
Clarify what is being launched:
- Product launch — new product, major version, public beta
- Feature launch — significant new capability
- Milestone announcement — funding, team, customer count, GitHub stars
- Open source launch — OSS release, new repo
Each has a different scope of effort.
Ask: What's being launched, and what is the goal? (Signups / GitHub stars / press coverage / community growth / enterprise pipeline)
Step 1: Launch Readiness Checklist
Before setting a launch date:
Product:
[ ] Product works reliably under load
[ ] Onboarding can be completed without help
[ ] Error states are handled gracefully (not 500 pages)
[ ] Mobile experience acceptable (if relevant)
Content:
[ ] Landing page copy updated to reflect new product/feature
[ ] Demo video or GIF created (30-60 seconds)
[ ] Screenshots updated
[ ] Docs updated for new functionality
Distribution assets:
[ ] Product Hunt listing drafted
[ ] HN Show HN post drafted
[ ] Twitter/X thread drafted
[ ] LinkedIn post drafted
[ ] Email to existing list drafted
[ ] Community announcement drafted (Discord/Slack)
Coordination:
[ ] Launch date set and team aligned
[ ] Support coverage scheduled for launch day
[ ] Person assigned to monitor and respond on each channel
[ ] Response playbook for likely objections/questions
Step 2: Product Hunt Launch Plan
Product Hunt is a snapshot of a day. Votes come in waves. Structure:
Pre-launch (2-4 weeks before):
- Create hunter network: ask 20-50 people to upvote on launch day. Real relationships only.
- Build PH presence: follow people, comment on others' launches to establish credibility.
- Prepare assets: logo, screenshots (×4), tagline (max 60 chars), description (max 260 chars)
Launch day:
- Post at 12:01 AM PST (start of day)
- Founder posts a personal comment at launch explaining the story
- Share PH link to: existing customers, email list, community, social — all at once in first 2 hours
- Monitor comments and respond within 30 minutes during business hours
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.
- 25d ago First seen · 207 lines · 60 tokens per session scan A f8cb6fb78213
buzz-launch is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 1,436 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-20.
Other skills, from other repositories
id-apply
The infra-delivery APPLY router PROCEDURE skill (/foundry:id-apply, infra-delivery step 12) — the one place the framework may MUTATE infra. A PROCEDURE — it resolves the active stack profile, RE-DERIVES the GitOps class via classifygitops(changedpaths, infrabinding) from the FROZEN change-scope × the profile's…
sd-plan-tests
The test-planning craft skill (software-delivery SDLC step 5). Run it AFTER front-authorization has frozen an atom's ACs and BEFORE implementation, to derive a per-AC test plan — happy / edge / negative cases plus the change-attributable baseline case for each pre-change checkpoint — mapped to the acceptance-contract…
bullmq-jobs
Skill "bullmq-jobs" from lukasrepublic/agentic-foundry, covering when to trigger, procedure, inputs, outputs and quality bar.
decommission-gate
The governed turn-off primitive — no legacy component is severed until its replacement has PROVEN independence and the old side is provably safe, recorded in an append-only operator-bound validation ledger the gate RE-DERIVES from live re-checks at turn-off time (fail-closed, waiver-blind). Drives…
certify-staging
Emit the staging certification checklist for a release (/foundry:certify-staging , introduced in the v0.25.0 certification realignment, CONSTITUTION.md §V factory-mode tail). Fills context/staging-checklist-template.md from the release manifest + the staging binding in .claude/foundry-project.json, observes deploy…
post-upgrade
The judgement half of a plugin upgrade (/foundry:post-upgrade). npx update-agentic-workspace@ does the deterministic half — marketplace refresh, plugin update, managed-file reconcile, the permission floor, the Amendments backfill, the permissions seed, the statusline wiring — and ends by writing…