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 Zenobia000/learn-claude-code --skill agent-buildergit clone --depth 1 https://github.com/Zenobia000/learn-claude-codeWrote 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/zenobia000/learn-claude-code/agent-builder)<a href="https://agentmods.dev/skills/zenobia000/learn-claude-code/agent-builder"><img src="https://agentmods.dev/badge/skills/zenobia000/learn-claude-code/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.
<a href="https://agentmods.dev/skills/zenobia000/learn-claude-code/agent-builder"><img src="https://agentmods.dev/badge/skills/zenobia000/learn-claude-code/agent-builder.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00125 | $0.01070 |
| Opus 5.5 | $0.00050 | $0.00428 |
| Sonnet 5.5 | $0.00025 | $0.00214 |
| Haiku 4.5 | $0.00013 | $0.00107 |
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 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.
This is a copy
100% identical to agent-builder — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Builder
Build AI agents for any domain - customer service, research, operations, creative work, or specialized business processes.
The Core Philosophy
The model already knows how to be an agent. Your job is to get out of the way.
An agent is not complex engineering. It's a simple loop that invites the model to act:
LOOP:
Model sees: context + available capabilities
Model decides: act or respond
If act: execute capability, add result, continue
If respond: return to user
That's it. The magic isn't in the code - it's in the model. Your code just provides the opportunity.
The Three Elements
1. Capabilities (What can it DO?)
Atomic actions the agent can perform: search, read, create, send, query, modify.
Design principle: Start with 3-5 capabilities. Add more only when the agent consistently fails because a capability is missing.
2. Knowledge (What does it KNOW?)
Domain expertise injected on-demand: policies, workflows, best practices, schemas.
Design principle: Make knowledge available, not mandatory. Load it when relevant, not upfront.
3. Context (What has happened?)
The conversation history - the thread connecting actions into coherent behavior.
Design principle: Context is precious. Isolate noisy subtasks. Truncate verbose outputs. Protect clarity.
Agent Design Thinking
Before building, understand:
- Purpose: What should this agent accomplish?
- Domain: What world does it operate in? (customer service, research, operations, creative...)
- Capabilities: What 3-5 actions are essential?
- Knowledge: What expertise does it need access to?
- Trust: What decisions can you delegate to the model?
CRITICAL: Trust the model. Don't over-engineer. Don't pre-specify workflows. Give it capabilities and let it reason.
Progressive Complexity
Start simple. Add complexity only when real usage reveals the need:
| Level | What to add | When to add it |
|---|---|---|
| Basic | 3-5 capabilities | Always start here |
| Planning | Progress tracking | Multi-step tasks lose coherence |
| Subagents | Isolated child agents | Exploration pollutes context |
| Skills | On-demand knowledge | Domain expertise needed |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 130 lines · 125 tokens per session scan A 4b88e0f4c19c
agent-builder is a skill published in the GitHub repository Zenobia000/learn-claude-code (11 stars, last pushed 3mo ago), licensed MIT. It adds 125 tokens to every session and 1,070 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to agent-builder, differing in 0 lines, and is treated as a copy.
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…