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 kychee-com/run402 --skill buzzgit clone --depth 1 https://github.com/kychee-com/run402Wrote 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/kychee-com/run402/buzz)<a href="https://agentmods.dev/skills/kychee-com/run402/buzz"><img src="https://agentmods.dev/badge/skills/kychee-com/run402/buzz/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/kychee-com/run402/buzz"><img src="https://agentmods.dev/badge/skills/kychee-com/run402/buzz.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Rogue Agent · line 16 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Excessive Agency · line 45 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00137 | $0.06454 |
| Opus 5.5 | $0.00055 | $0.02582 |
| Sonnet 5.5 | $0.00027 | $0.01291 |
| Haiku 4.5 | $0.00014 | $0.00645 |
Grade A, and why
run402-buzz 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 5d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run402 for Buzz
Keep the Buzz/Nostr key and Run402 wallet key separate. Link their public identities with the existing dual-proof ceremony; never derive, import, export, or expose either private key.
Buzz and Run402 treat people and agents as first-class participants. Each person or agent acts through its own identity and keeps an attributable history. Equal standing never means shared credentials or equal permissions: Run402 memberships, grants, grant keys, freshness, and spend policy still determine authority.
Keep the authority domains explicit. Buzz is authoritative for signed collaboration evidence. Run402 is authoritative for organizations, project authority, deploys, leases, billing, delivery attempts, and runtime receipts. Identity links and receipts connect the records; Buzz proof is evidence, never Run402 authentication or authorization.
Copying, updating, or discovering the skill files performs no setup and grants no authority. In a managed Buzz conversation, the canonical request Please install the run402.com skill is nevertheless a goal-shaped request to install and connect Run402: after the inert files are verified, continue in the same turn through preflight, setup, and public identity-link verification. Stop after file installation only when the human explicitly says to copy/install the files only or says not to set up or connect Run402.
Install or update this skill
Read references/installation.md when installing, updating, repairing, or reporting this skill. Use first-party discovery at https://run402.com, the exact managed-runtime target, and the bounded transport-only GitHub fallback defined there. An integrity failure or ambiguous failure stops before setup with mutation_state: "not_started"; never hide it by changing source. Installation itself remains inert. After verifying the installed package and target path, immediately read the installed SKILL.md from that verified path and continue with the setup workflow below in the current turn. Do not say that the skill will be available on the next turn, ask whether to set up Run402, or stop at the installation receipt unless the human explicitly requested files only or prohibited setup/connection.
What ships with it
26 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.
- fixtures/buzz-relay-v0.2.1-notification-capability.json 927 B
- fixtures/buzz-relay-v0.2.1-notification-kind9.json 3.7 KB
- fixtures/buzz-relay-v0.2.1-notification-membership.json 2.0 KB
- fixtures/buzz-relay-v0.2.1-notification-tombstone.json 1.1 KB
- fixtures/buzz-v0.4.26-desktop-owner-negative.json 1.8 KB
- fixtures/buzz-v0.4.26-managed-agent-kind1.json 2.0 KB
- fixtures/buzz-v0.5.2-browser-fragment-v1.json 4.4 KB
- fixtures/buzz-v0.5.2-cli-capabilities.json 2.6 KB
- fixtures/buzz-v0.5.2-community-authority.json 4.8 KB
- fixtures/identity-link-v1-golden.json 8.7 KB
- fixtures/run402-buzz-doctor-v1-contract.json 3.1 KB
- helper.test.mjs 3.9 KB runs code
- install-smoke.mjs 8.1 KB runs code
- package.test.mjs 14 KB runs code
- README.md 10 KB
- references/community-control-plane.md 12 KB
- references/conversations.md 2.0 KB
- references/identity-and-security.md 4.4 KB
- references/installation.md 6.0 KB
- references/preflight.md 7.6 KB
- references/receipts.md 3.6 KB
- scripts/buzz-publish-proof.mjs 5.3 KB runs code
- scripts/doctor-report.mjs 4.0 KB runs code
- scripts/setup.mjs 37 KB runs code
- scripts/strict-json.mjs 4.1 KB runs code
- setup.test.mjs 38 KB runs code
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.
- 5d ago Changed · +18 tokens per session 359da8fb7715
- 6d ago Changed · +10 lines 2e1a5139d377
- 25d ago Changed ed9fa71bcdfd
- 1mo ago Changed · +19 lines 8102cc05de40
- 1mo ago Changed · +16 lines 04ce7a726af9
- 1mo ago Changed · +4 lines 1f45866cf165
- 1mo ago First seen · 157 lines · 119 tokens per session scan A aa74be99ce0e
run402-buzz is a skill published in the GitHub repository kychee-com/run402 (24 stars, last pushed today), licensed MIT. It adds 137 tokens to every session and 6,454 once invoked, about $0.0005 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 skills, from other repositories
butterbase
AI-native, open-source backend-as-a-service with a built-in Model Context Protocol server. Postgres, auth, storage, functions, AI gateway.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-mirror
Stand up a persistent, self-refreshing local mirror of a bulk upstream dataset with the MirrorService (@cyanheads/mcp-ts-core/mirror). Use when a server wraps a large or slow API and should query a synced local index (embedded SQLite + FTS5) instead of paginating the live API per request.
build-app
Use when building a new Butterbase app from scratch, creating a full-stack application, or when the user asks to set up a complete backend with database, auth, and deployment.
schema-design
Use when designing database schemas, creating or modifying tables, choosing column types, adding indexes, or working with the Butterbase declarative schema DSL.
debug-rls
Use when users report access denied errors, see wrong data, RLS policies are not working, or when troubleshooting Row-Level Security issues in Butterbase.