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 leecyno1/boutique-skills --skill agent-buildergit clone --depth 1 https://github.com/leecyno1/boutique-skillsWrote 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/leecyno1/boutique-skills/agent-builder)<a href="https://agentmods.dev/skills/leecyno1/boutique-skills/agent-builder"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/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/leecyno1/boutique-skills/agent-builder"><img src="https://agentmods.dev/badge/skills/leecyno1/boutique-skills/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.00093 | $0.00793 |
| Opus 5 | $0.00046 | $0.00396 |
| Sonnet 5 | $0.00019 | $0.00159 |
| Haiku 4.5 | $0.00009 | $0.00079 |
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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- openclaw-agent-builder — 94% identical, 40 lines differ
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Builder (OpenClaw)
Design and generate a complete OpenClaw agent workspace with strong defaults and advanced-user-oriented clarifying questions.
Canonical references
- Workspace layout + heartbeat rules: Read
references/openclaw-workspace.md - File templates/snippets: Read
references/templates.md - Optional background (generic agent architecture):
references/architecture.md
Workflow: build an agent from scratch
Phase 1 — Interview (ask clarifying questions)
Ask only what you need; keep it tight. Prefer multiple short rounds over one giant questionnaire.
Minimum question set (advanced):
- Job statement: What is the agent’s primary mission in one sentence?
- Surfaces: Which channels (Telegram/WhatsApp/Discord/iMessage)? DM only vs groups?
- Autonomy level:
- Advisor (suggest only)
- Operator (non-destructive ok; ask before destructive/external)
- Autopilot (broad autonomy; higher risk)
- Hard prohibitions: Any actions the agent must never take?
- Memory: Should it keep curated
MEMORY.md? What categories matter? - Tone: concise vs narrative; strict vs warm; profanity rules; “not the user’s voice” in groups?
- Tool posture: tool-first vs answer-first; verification requirements.
Phase 2 — Generate workspace files
Generate these files (minimum viable OpenClaw agent):
IDENTITY.mdSOUL.mdAGENTS.mdUSER.mdHEARTBEAT.md(often empty by default)
Optionals:
MEMORY.md(private sessions only)memory/YYYY-MM-DD.mdseed (today) with a short “agent created” entryTOOLS.mdstarter (if the user wants per-environment notes)
Use templates from references/templates.md but tailor content to the answers.
Phase 3 — Guardrails checklist
Ensure the generated agent includes:
- Explicit ask-before-destructive rule.
- Explicit ask-before-outbound-messages rule.
- Stop-on-CLI-usage-error rule.
- Max-iteration / loop breaker guidance.
- Group chat etiquette.
- Sub-agent note: essential rules live in
AGENTS.md.
What ships with it
4 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.
- 9d ago First seen · 89 lines · 93 tokens per session scan A 92794b52a1c3
agent-builder is a skill published in the GitHub repository leecyno1/boutique-skills (5 stars, last pushed 19d ago), licensed MIT. It adds 93 tokens to every session and 793 once invoked, about $0.0005 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…