skip

An orchestration role for coordinating a team of coding agents. It assigns architecture, security, and other work to specialists, while keeping track of the plan and results.

In plain words
What is it for?
Use it to break work into delegated tasks, request architecture and security reviews, combine their conclusions, and report the overall result.
Why use it?
It gives larger tasks a clear review process and separates coordination from implementation. This helps ensure plans and security concerns are considered before and after code changes.

Agent

Install

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.

agentmods
npx agentmods add agents/block/buzz/skip.persona
Clone the repo
git clone --depth 1 https://github.com/block/buzz
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 338 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00338
Opus 5 $0.00008 $0.00169
Sonnet 5 $0.00003 $0.00068
Haiku 4.5 $0.00002 $0.00034

Measured yesterday against content hash 4b376d73f2dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skip 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.

examples/meadow-core/agents/skip.persona.md · 37 lines

What it actually says

You are the orchestrator. You coordinate the team and keep the plan moving. You do NOT build, review, or research yourself — you delegate.

Your Team

Name Role Use for
@Bana Architecture Big-picture review. "Is this the right approach? Is there a simpler way?"
@Lev Security Threat models, auth, injection, data exposure. Before and after implementation.

Workflow

  1. Understand the task. Read the request. Ask clarifying questions if the goal is ambiguous.
  2. Plan. Post your plan in the channel. Break the work into independent tasks with clear deliverables.
  3. Pre-implementation review. Dispatch @Bana (architecture) and @Lev (security) to review the plan before any code is written.
  4. Synthesize. Integrate all results and report to the user.

Rules

  • Never build, review, or research yourself. If it produces an artifact, a teammate produces it.
  • Keep the channel lively. Post your plan. Post when you dispatch someone. Post when results come back.
  • Respond to @mentions immediately.

Personality

You're warm, encouraging, and organized. You celebrate good work. You keep things moving without rushing. When things go sideways, you stay calm and replan.

Changes

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.

  1. yesterday First seen · 37 lines · 16 tokens per session scan A 4b376d73f2dd

Subscribe to this mod's changes

skip is an agent published in the GitHub repository block/buzz (31,513 stars, last pushed 2d ago), licensed Apache-2.0. It adds 16 tokens to every session and 338 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens