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/adnanakil/nobuzz/debuzznpx skills add adnanakil/nobuzz --skill debuzzgit clone --depth 1 https://github.com/adnanakil/nobuzzWrote 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/adnanakil/nobuzz/debuzz)<a href="https://agentmods.dev/skills/adnanakil/nobuzz/debuzz"><img src="https://agentmods.dev/badge/skills/adnanakil/nobuzz/debuzz.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.00125 | $0.01224 |
| Opus 5 | $0.00063 | $0.00612 |
| Sonnet 5 | $0.00025 | $0.00245 |
| Haiku 4.5 | $0.00013 | $0.00122 |
Grade A, and why
debuzz 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 3d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debuzz — plain-English translation via Antigravity
The user finds Claude's default register grating: dramatic framing, suspense-building, listicle energy, phrases like "the load-bearing assumption" or "the third one is the most instructive yet." This skill reruns a response through the agy CLI (Google Antigravity) so they get the same content said like a normal person, at a chosen altitude. The point of using Antigravity (rather than rewriting it yourself) is an independent editor that doesn't share the original's stylistic habits — so do not paraphrase, tidy, or summarize the source text before or after the agy call.
Arguments
/debuzz [mode] [text] — both parts optional.
- mode: if the first word of the arguments is
colleague,manager, ordirector, that's the mode. Otherwise the mode iscolleague. - text: whatever remains after the mode word is the text to translate. If empty, translate your own most recent substantive response — the one immediately before the user invoked the skill. Reproduce it faithfully from the conversation, word for word, including code blocks.
Examples: /debuzz (colleague mode, last reply) · /debuzz director (exec brief of last reply) · /debuzz manager <pasted text>.
Modes
Every mode shares the same style rules: plain declarative sentences, no dramatic framing, no suspense-building, no buzzy metaphors ("load-bearing assumption", "here's the kicker", "this changes everything"), no reveals, no hype. The modes differ only in audience and altitude:
- colleague (default) — a competent engineer explaining it to a peer. Keep every technical fact, number, file path, command, and code block exactly intact. Only the style changes, not the substance; do not shorten beyond what removing fluff removes.
- manager — an engineer updating a technical-adjacent manager. Lead with what happened / what was found, why it matters, and what happens next or what's needed. Keep key facts and numbers; drop code blocks, file paths, and implementation mechanics unless one is essential to the point. Target roughly a third of the original length.
- director — an executive brief. Three to five sentences: the outcome, the impact or risk in business terms, and any decision or ask. No code, no file paths, no implementation detail. Assume thirty seconds of attention.
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.
- 3d ago First seen · 48 lines · 125 tokens per session scan A ae87b65309d9
debuzz is a skill published in the GitHub repository adnanakil/nobuzz (244 stars, last pushed 12d ago), licensed MIT. It adds 125 tokens to every session and 1,224 once invoked, about $0.0006 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…