ai-tools-setup

ai-tools-setup is a command for Claude Code from Matt-Dionis/claude-code-configs. It costs 7 tokens per session (864 once invoked), scanned A, original, MIT.

A setup guide for giving an AI application tools it can call, such as utility functions, database queries, external APIs, or document-processing actions. The tools use defined inputs that can be checked before execution.

In plain words
What is it for?
Use it to create calculators, validators, safe database access, API integrations, webhooks, document or image processing, and multi-step agent workflows.
Why use it?
It helps control how AI-triggered actions run by adding validation, authentication, authorization, sanitisation, rate limits, error handling, and monitoring.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to create calculators, validators, safe database access, API integrations, webhooks, document or image processing, and multi-step agent workflows.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/matt-dionis/claude-code-configs/ai-tools-setup
Install

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.

Clone the repo
git clone --depth 1 https://github.com/Matt-Dionis/claude-code-configs

Made for: Claude Code.

Wrote 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.

agentmods badge for ai-tools-setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/ai-tools-setup/github.svg)](https://agentmods.dev/commands/matt-dionis/claude-code-configs/ai-tools-setup)
Your own site
<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.

agentmods 80×15 button for ai-tools-setup

Your own site · 80×15
<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>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 864 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 3c207b25dee0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

configurations/tooling/vercel-ai-sdk/.claude/commands/ai-tools-setup.md · 138 lines

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

  1. Analyze the project needs and identify appropriate tool types
  2. Design tool schemas with proper Zod validation
  3. Implement secure execution logic with error handling
  4. Set up proper authentication and authorization
  5. Add comprehensive input validation and sanitization
  6. Implement rate limiting and usage monitoring
  7. Create tool testing suite for reliability
  8. 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

Read the full file on GitHub · 138 lines

Changes

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.

  1. 1mo ago First seen · 138 lines · 7 tokens per session scan A 3c207b25dee0

Subscribe to this mod's changes

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.