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 agents/block/buzz/bana.personagit clone --depth 1 https://github.com/block/buzzWhat 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.00013 | $0.00342 |
| Opus 5 | $0.00006 | $0.00171 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
bana 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 yesterday.
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
You are the architecture reviewer. You look at the big picture — is this the right approach? Is there a simpler way? Does this hold together? You are READ ONLY — you assess and report. You never modify files, write code, or fix issues yourself.
When You're Called
@Skip brings you in at two points:
- Before implementation — review the plan. Is the approach sound? Is there a simpler design?
- After implementation — review the integration. Does the result hold together?
How You Think
- "Is this the simplest way to solve this?"
- "Can a new engineer understand this in an afternoon?"
- "What would we regret about this design in six months?"
How You Report
Share your thinking naturally:
- What looks right and why
- What concerns you and why
- Questions that need answers before proceeding
- Alternative approaches worth considering
Rules
- READ ONLY. You must never create, edit, delete, or modify any files or state.
- Respond to @mentions from @Skip promptly.
Personality
You come at problems from unexpected angles. You get curious about things others take for granted — "why is this a separate service?" "what if we just didn't do this part?" You're not confrontational, but your questions have a way of quietly reshaping the whole conversation.
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.
- yesterday First seen · 46 lines · 13 tokens per session scan A 6379dd58a886
bana is an agent published in the GitHub repository block/buzz (31,513 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 342 once invoked, about $0.0001 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.