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-chat-setup)<a href="https://agentmods.dev/commands/matt-dionis/claude-code-configs/ai-chat-setup"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/ai-chat-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-chat-setup"><img src="https://agentmods.dev/badge/commands/matt-dionis/claude-code-configs/ai-chat-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.00009 | $0.00501 |
| Opus 5.5 | $0.00004 | $0.00200 |
| Sonnet 5.5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
ai-chat-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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up AI Chat Interface
Create a production-ready chat interface with the Vercel AI SDK based on the specified type: $ARGUMENTS
Project Context
Current project structure: !find . -type f -name "*.json" -o -name "*.ts" -o -name "*.tsx" | head -10
Current dependencies: !cat package.json | jq '.dependencies // {}' 2>/dev/null || echo "No package.json found"
Requirements Analysis
Based on the requested chat type ($ARGUMENTS), I'll implement:
Basic Chat: Simple text-based streaming chat interface
Advanced Chat: Enhanced UI with message history, error handling, and optimizations
Multimodal Chat: Support for images, PDFs, and file uploads
RAG Chat: Retrieval-augmented generation with knowledge base
Agent Chat: Tool-calling agents with function execution
Your Task
- Analyze the current project structure to understand the existing setup
- Install required dependencies if not already present
- Create the appropriate chat implementation based on the specified type
- Set up the API route with proper streaming and error handling
- Implement the React component with modern UI patterns
- Add proper TypeScript types for type safety
- Include error boundaries and loading states
- Test the implementation and provide usage instructions
Implementation Guidelines
- Use the latest AI SDK patterns and best practices
- Implement proper error handling and loading states
- Add TypeScript types for all interfaces
- Follow Next.js App Router conventions
- Include proper accessibility features
- Use modern React patterns (hooks, Suspense, etc.)
- Add responsive design considerations
- Implement proper security measures
Expected Deliverables
- API route handler (
app/api/chat/route.ts) - Chat component (
components/chat.tsxor similar) - Required TypeScript types
- Updated package.json dependencies
- Basic styling (Tailwind classes)
- Usage documentation and examples
Focus on creating a robust, production-ready implementation that follows AI SDK best practices and modern web development standards.
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 · 9 tokens per session scan A 8e871962be5f
ai-chat-setup is a command published in the GitHub repository Matt-Dionis/claude-code-configs (619 stars, last pushed 1y ago), licensed MIT. It adds 9 tokens to every session and 501 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
querying
Query documents from a search index using type-safe filters with support for pagination, sorting, field selection, scoring, and highlighting. Count matching documents efficiently without returning results.
agent
Add an AI agent / RAG backend (@convex-dev/agent) to the Convex app.
ingest
Manually add knowledge to the Weaviate store.
inference.embed
Embed one or more texts into vectors.
vector.batch_exists
Check existence for multiple vector keys.
vector.batch_upsert
Upsert multiple vectors in one itemwise batch.