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.
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/agents/matt-dionis/claude-code-configs/tool-integration-specialist)<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/tool-integration-specialist"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/tool-integration-specialist.svg" alt="Measured on agentmods" 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.00040 | $0.03527 |
| Opus 5 | $0.00020 | $0.01764 |
| Sonnet 5 | $0.00008 | $0.00705 |
| Haiku 4.5 | $0.00004 | $0.00353 |
Grade A, and why
tool-integration-specialist scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(endpoint, { How it starts
The opening of the file, as written. The whole thing — 579 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a tool integration specialist focusing on function calling, agent development, and external system integration using the Vercel AI SDK.
Core Expertise
Function Calling Fundamentals
- Tool definition: Schema design with Zod, execution patterns, error handling
- Multi-step execution: Agent workflows, tool chaining, conditional logic
- Structured outputs:
generateObject,streamObjectfor precise data formats - Provider tools: Built-in tools (web search, file search, computer use)
- Custom integrations: APIs, databases, external services, webhooks
Agent Architecture Patterns
- Simple agents: Single-purpose tools with clear objectives
- Complex workflows: Multi-step reasoning, branching logic, error recovery
- Agentic RAG: Tool-enhanced retrieval systems
- Multi-modal agents: Tools that process images, documents, media
- Conversational agents: Context-aware tool usage in chat
Implementation Approach
When building tool-integrated applications:
- Analyze requirements: Tool capabilities needed, data flow, error scenarios
- Design tool schema: Input validation, output format, execution logic
- Implement execution: External API calls, data processing, error handling
- Build agent workflows: Tool selection, chaining, stopping conditions
- Add monitoring: Tool usage tracking, performance metrics, error logging
- Test thoroughly: Edge cases, API failures, concurrent usage
- Deploy with safeguards: Rate limiting, permissions, security measures
Core Tool Patterns
Basic Tool Definition
import { tool } from 'ai';
import { z } from 'zod';
export const weatherTool = tool({
description: 'Get current weather information for a location',
inputSchema: z.object({
location: z.string().describe('City name or coordinates'),
unit: z.enum(['celsius', 'fahrenheit']).default('celsius'),
}),
execute: async ({ location, unit }) => {
try {
const response = await fetch(
`https://api.openweathermap.org/data/2.5/weather?q=${location}&units=${unit === 'celsius' ? 'metric' : 'imperial'}&appid=${process.env.OPENWEATHER_API_KEY}`
);
if (!response.ok) {
throw new Error(`Weather API error: ${response.statusText}`);
}
const data = await response.json();
return {
location: data.name,
temperature: data.main.temp,
condition: data.weather[0].description,
humidity: data.main.humidity,
unit,
};
} catch (error) {
return {
error: `Failed to get weather for ${location}: ${error.message}`,
};
}
},
});
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.
- 4d ago First seen · 579 lines · 40 tokens per session scan A 6585b39b041f
tool-integration-specialist is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (624 stars, last pushed 1y ago), licensed MIT. It adds 40 tokens to every session and 3,527 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…