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/commands/matt-dionis/claude-code-configs/ai-tools-setup)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/ai-tools-setup"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/ai-tools-setup/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/commands/matt-dionis/claude-code-configs/ai-tools-setup"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/ai-tools-setup.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.00007 | $0.00864 |
| Opus 5.5 | $0.00003 | $0.00346 |
| Sonnet 5.5 | $0.00001 | $0.00173 |
| Haiku 4.5 | $0.00001 | $0.00086 |
Grade A, and why
ai-tools-setup 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.
How it starts
The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up AI Tools and Function Calling
Create comprehensive AI tool integrations with the Vercel AI SDK for: $ARGUMENTS
Current Project Analysis
Existing tool implementations: !grep -r "import.*tool" . --include="*.ts" --include="*.tsx" | head -5
API integrations: !grep -r "fetch\|axios" . --include="*.ts" | head -5
Database setup: !find . -name "*schema*" -o -name "*db*" -o -name "*database*" | grep -v node_modules | head -5
Tool Type Requirements
Simple Tools: Basic utility functions (calculator, formatter, validator) Database Tools: Safe database queries, data retrieval, analytics API Tools: External service integrations, webhooks, data fetching Multimodal Tools: Image processing, document analysis, file handling Agent Tools: Complex workflows, multi-step operations, decision making
Your Task
- Analyze the project needs and identify appropriate tool types
- Design tool schemas with proper Zod validation
- Implement secure execution logic with error handling
- Set up proper authentication and authorization
- Add comprehensive input validation and sanitization
- Implement rate limiting and usage monitoring
- Create tool testing suite for reliability
- Document tool usage and examples
Implementation Guidelines
Tool Definition Patterns
// Basic tool structure
const toolName = tool({
description: 'Clear description of what the tool does',
inputSchema: z.object({
param: z.string().describe('Parameter description'),
}),
execute: async ({ param }) => {
// Implementation with proper error handling
try {
const result = await performOperation(param);
return { success: true, data: result };
} catch (error) {
return { success: false, error: error.message };
}
},
});
Security Considerations
- Input validation and sanitization
- Authentication and authorization checks
- Rate limiting and abuse prevention
- Secure API key management
- Output filtering and validation
- Audit logging for sensitive operations
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 · 138 lines · 7 tokens per session scan A 3c207b25dee0
ai-tools-setup is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 864 once invoked, about $0.0000 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-09-03.
Other commands, from other repositories
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
music-suno-prompt
Grounded Suno prompt synthesis from local knowledge corpus + persona canon + label canon. No vibes-prompting.
audit-prompt
Evaluate an existing prompt for clarity, effectiveness, and edge cases.
laravel-ai-sdk
Build AI features with the first-party Laravel AI SDK (Laravel 13+); use the laravel:ai-sdk skill exactly as written.
vlm-ocr-evaluation
Run the vlm-ocr skill in its evaluate phase: compare candidate OCR systems against a stratified human-transcribed ground-truth sample and pick a model on measured CER/WER before committing to a bulk run.
dare-llm-integration
Integração segura e eficiente com LLMs (Gemini, Claude, OpenAI, Ollama) em projetos DARE.