agent-builder

agent-builder is a skill for Claude Code from mike-coulbourn/claude-vibes. It costs 54 tokens per session (3,125 once invoked), scanned A, original, MIT.

A guide for creating specialized Claude Code agents, which are assistants configured for particular tasks and run in separate working contexts.

In plain words
What is it for?
Designing agents, writing their YAML settings and prompts, limiting what they can do, and placing them at project or personal scope.
Why use it?
It explains how to control an agent’s instructions, available tools, model, permissions, and automatic skill loading.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: reads .claude/ paths; mentions subagents; names the AskUserQuestion tool.

Part of the claude-vibes plugin — 24 skills shipped together

Good fit Designing agents, writing their YAML settings and prompts, limiting what they can do, and placing them at project or personal scope.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/mike-coulbourn/claude-vibes/agent-builder
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.

Any agent
npx skills add mike-coulbourn/claude-vibes --skill agent-builder
Clone the repo
git clone --depth 1 https://github.com/mike-coulbourn/claude-vibes

Made for: Claude Code.

Or install claude-vibes, the plugin that ships this one along with the rest of its 24 skills.

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

agentmods badge for agent-builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/mike-coulbourn/claude-vibes/agent-builder/github.svg)](https://agentmods.dev/skills/mike-coulbourn/claude-vibes/agent-builder)
Your own site
<a href="https://agentmods.dev/skills/mike-coulbourn/claude-vibes/agent-builder"><img src="https://agentmods.dev/badge/skills/mike-coulbourn/claude-vibes/agent-builder/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.

agentmods 80×15 button for agent-builder

Your own site · 80×15
<a href="https://agentmods.dev/skills/mike-coulbourn/claude-vibes/agent-builder"><img src="https://agentmods.dev/badge/skills/mike-coulbourn/claude-vibes/agent-builder.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,125 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00054 $0.03125
Opus 5 $0.00027 $0.01563
Sonnet 5 $0.00011 $0.00625
Haiku 4.5 $0.00005 $0.00313

Measured 10d ago against content hash ff52e0b5cef4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

agent-builder 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 10d 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.

plugins/vibes/skills/agent-builder/SKILL.md · 476 lines

How it starts

The opening of the file, as written. The whole thing — 476 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Builder

A comprehensive guide for creating custom agents in Claude Code. Agents are specialized AI assistants that run in separate context windows, enabling focused, autonomous task execution.


Quick Reference

YAML Frontmatter Fields

Field Required Description
name Yes Unique identifier (lowercase-with-hyphens)
description Yes When to invoke — critical for discovery
tools No Allowed tools (inherits all if omitted)
model No haiku, sonnet, opus, or inherit
permissionMode No default, acceptEdits, bypassPermissions, plan
skills No Auto-load Skills when agent starts

File Locations

Scope Location Use Case
Project .claude/agents/agent-name.md Team workflows (git-shared)
Personal ~/.claude/agents/agent-name.md Individual use (all projects)

Common Tool Patterns

# Read-only (safest)
tools: Read, Grep, Glob

# File modification
tools: Read, Write, Edit, Grep, Glob

# Git operations only
tools: Bash(git:*)

# Specific commands
tools: Bash(npm test:*), Bash(npm run:*), Read, Grep

# Full shell (use sparingly)
tools: Bash

Model Selection Guide

Model Best For Tradeoff
haiku Quick checks, simple tasks Fast, cheap, less capable
sonnet Balanced work (default) Good balance
opus Complex analysis, critical tasks Most capable, slower, expensive
inherit Consistency with main conversation Adapts to user's model

6-Phase Workflow

Phase 1: Requirements Gathering

Use AskUserQuestion to understand what the user needs:

Key Questions:

  1. What task should this agent handle?
  2. What expertise/role should it have?
  3. Who will use it — team or personal?
  4. What should it be able to do vs NOT do?
  5. How should it present results?

Example Questions:

What specific task should this agent handle?
├── Code review (quality, security, style)
├── Debugging (error investigation, root cause)
├── Testing (run tests, fix failures)
├── Documentation (generate, verify, update)
└── Other: [describe]

Who will use this agent?
├── Just me (personal: ~/.claude/agents/)
├── My team (project: .claude/agents/)

Read the full file on GitHub · 476 lines

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. 10d ago First seen · 476 lines · 54 tokens per session scan A ff52e0b5cef4

Subscribe to this mod's changes

agent-builder is a skill published in the GitHub repository mike-coulbourn/claude-vibes (39 stars, last pushed 8mo ago), licensed MIT. It adds 54 tokens to every session and 3,125 once invoked, about $0.0003 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

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

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…

vercel/next.js · 95 tokens

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…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens