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 pinkpixel-dev/skills-collection-1 --skill agent-tool-buildergit clone --depth 1 https://github.com/pinkpixel-dev/skills-collection-1Wrote 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/pinkpixel-dev/skills-collection-1/agent-tool-builder)<a href="https://agentmods.dev/skills/pinkpixel-dev/skills-collection-1/agent-tool-builder"><img src="https://agentmods.dev/badge/skills/pinkpixel-dev/skills-collection-1/agent-tool-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/pinkpixel-dev/skills-collection-1/agent-tool-builder"><img src="https://agentmods.dev/badge/skills/pinkpixel-dev/skills-collection-1/agent-tool-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.00054 | $0.00358 |
| Opus 5.5 | $0.00022 | $0.00143 |
| Sonnet 5.5 | $0.00011 | $0.00072 |
| Haiku 4.5 | $0.00005 | $0.00036 |
Grade A, and why
agent-tool-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.
Copies of this mod
3 near-identical copies found in the catalogue:
- agent-tool-builder — 100% identical, 0 lines differ
- agent-tool-builder — 100% identical, 0 lines differ
- agent-tool-builder — 100% identical, 0 lines differ
What it actually says
Agent Tool Builder
You are an expert in the interface between LLMs and the outside world. You've seen tools that work beautifully and tools that cause agents to hallucinate, loop, or fail silently. The difference is almost always in the design, not the implementation.
Your core insight: The LLM never sees your code. It only sees the schema and description. A perfectly implemented tool with a vague description will fail. A simple tool with crystal-clear documentation will succeed.
You push for explicit error hand
Capabilities
- agent-tools
- function-calling
- tool-schema-design
- mcp-tools
- tool-validation
- tool-error-handling
Patterns
Tool Schema Design
Creating clear, unambiguous JSON Schema for tools
Tool with Input Examples
Using examples to guide LLM tool usage
Tool Error Handling
Returning errors that help the LLM recover
Anti-Patterns
❌ Vague Descriptions
❌ Silent Failures
❌ Too Many Tools
Related Skills
Works well with: multi-agent-orchestration, api-designer, llm-architect, backend
When to Use
This skill is applicable to execute the workflow or actions described in the overview.
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 · 59 lines · 54 tokens per session scan A a85c9bbad171
agent-tool-builder is a skill published in the GitHub repository pinkpixel-dev/skills-collection-1 (9 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 54 tokens to every session and 358 once invoked, about $0.0002 per session on Opus 5.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
find-awesome-tools
Discovers curated tools, libraries, frameworks, and resources across thousands of awesome-lists. Use this skill whenever the user is shopping for options in a technology space — "what are good Rust CLI argument parsers", "recommend React state management libraries", "popular Python web frameworks", "tools for building…
agent-self-scheduling
Schedule AI agent runs with cron, loops, or external clocks while avoiding unsafe tight autonomous timers.
ai-agent-evaluation-benchmarking
Autonomous AI agent benchmark evaluation register: task completion rates, planning accuracy, tool invocation precision, and cost benchmarks.
ai-agent-tool-routing
Autonomous AI agent tool router register: schema registration, runtime parameter coercion, idempotency keys, and error recovery policies.
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.