Buzz is a self-hostable workspace where people and AI agents share rooms, communicate through signed events, and collaborate on repositories, workflows, canvases, and code reviews. It is for teams that want humans and agents to work together on software through a relay they control. The catalogue entries are agents, skills, and instructions for using Buzz’s collaborative workflows.
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 block/buzz --skill github-researchgit clone --depth 1 https://github.com/block/buzzWrote 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/block/buzz/github-research)<a href="https://agentmods.dev/skills/block/buzz/github-research"><img src="https://agentmods.dev/badge/skills/block/buzz/github-research/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/block/buzz/github-research"><img src="https://agentmods.dev/badge/skills/block/buzz/github-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00019 | $0.00382 |
| Opus 5.5 | $0.00008 | $0.00153 |
| Sonnet 5.5 | $0.00004 | $0.00076 |
| Haiku 4.5 | $0.00002 | $0.00038 |
Grade A, and why
github-research 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 1mo 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
GitHub Research
Search GitHub for prior art, implementation patterns, and maintainer decisions.
Commands
# Search issues
gh search issues "topic" --repo owner/repo --limit 20 \
--json number,title,state,url
# Search merged PRs (highest signal)
gh search prs "topic" --repo owner/repo --merged --limit 20 \
--json number,title,url
# Search code (use query syntax for path filtering)
gh search code "pattern path:src/" --repo owner/repo --limit 20 \
--json path,textMatches
# Get full issue or PR details
gh issue view 123 --repo owner/repo --json number,title,body,comments
gh pr view 456 --repo owner/repo --json number,title,body,reviews,files
Rate Limits
- Search API: 30 requests/minute
- Check with:
gh api rate_limit --jq '.resources.search'
Signal Ranking
- Merged PRs — decisions that shipped
- Maintainer comments — authoritative
- Closed issues with solutions — problems solved
- Open issues — current problems (lower signal)
Report Format
## Research: [Topic]
### Summary
- Key finding 1 [#123]
- Key finding 2 [PR #456]
### Findings
1. **#123: [Title]** — [summary]. URL: https://...
2. **PR #456: [Title]** — [what it changed]. URL: https://...
### Gaps
- [What you looked for but didn't find]
Always include URLs. If nothing relevant exists, say so.
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.
- 1mo ago First seen · 60 lines · 19 tokens per session scan A c9b68613be2b
github-research is a skill published in the GitHub repository block/buzz (36,020 stars, last pushed today), licensed Apache-2.0. It adds 19 tokens to every session and 382 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…