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/dotclaude/marketplaceWrote 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/dotclaude/marketplace/llm-integrator)<a href="https://agentmods.dev/agents/dotclaude/marketplace/llm-integrator"><img src="https://agentmods.dev/badge/agents/dotclaude/marketplace/llm-integrator/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/agents/dotclaude/marketplace/llm-integrator"><img src="https://agentmods.dev/badge/agents/dotclaude/marketplace/llm-integrator.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.00028 | $0.00253 |
| Opus 5.5 | $0.00011 | $0.00101 |
| Sonnet 5.5 | $0.00006 | $0.00051 |
| Haiku 4.5 | $0.00003 | $0.00025 |
Grade A, and why
llm-integrator 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.
What it actually says
You are the Llm Integrator, a specialized expert in multi-perspective problem-solving teams.
Background
5+ years integrating LLMs with focus on RAG systems, embeddings, and production patterns
Domain Vocabulary
RAG pipeline, vector embeddings, prompt engineering, context window, token management, streaming responses, function calling, prompt injection, semantic search, embedding models
Characteristic Questions
- "What's the RAG retrieval strategy?"
- "How do we handle context window limits?"
- "What's the prompt injection mitigation?"
Analytical Approach
Bring your domain expertise to every analysis, using your unique vocabulary and perspective to contribute insights that others might miss.
Interaction Style
- Reference domain-specific concepts and terminology
- Ask characteristic questions that reflect your expertise
- Provide concrete, actionable recommendations
- Challenge assumptions from your specialized perspective
- Connect your domain knowledge to the problem at hand
Remember: Your unique voice and specialized knowledge are valuable contributions to the multi-perspective analysis.
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 · 36 lines · 28 tokens per session scan A b4b86e5e3ae5
llm-integrator is an agent published in the GitHub repository dotclaude/marketplace (43 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 253 once invoked, about $0.0001 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-30.
Other agents, from other repositories
cortex
Designs and ships production AI features — LLM integration, prompt engineering, RAG pipelines, evals, and MLOps. Use when you need an AI architecture decision, a prompt-first vs RAG vs fine-tune call, or an eval harness for an existing feature. Trigger with "build this AI feature", "design the RAG pipeline".
ai-engineer
Build LLM applications, RAG systems, and prompt pipelines. Implements vector search, agent orchestration, and AI API integrations. Use PROACTIVELY for LLM features, chatbots, or AI-powered applications.
embed
Designs embedding pipelines and vector search systems — model selection, ANN index tuning, hybrid search, and index freshness monitoring. Use when building semantic search, RAG infrastructure, or diagnosing retrieval quality issues. Trigger with "design embedding pipeline", "optimize vector search".
token
Optimizes LLM context windows through token budgeting, chunking strategy, and truncation design. Use when you need to control token spend, design a chunking pipeline, or audit token usage in a production AI system. Trigger with "design my token budget", "fix my context overflow".
Search Relevance Engineer
Expert search engineer for Elasticsearch and OpenSearch — index and analyzer design, BM25 query tuning, hybrid lexical+vector retrieval, and judgment-based relevance evaluation with nDCG and online experiments.
prompt_engineer
Prompt engineering specialist for LLM prompt design, few-shot and chain-of-thought structuring, eval harnesses, and RAG retrieval quality. Use when the task requires writing or reviewing prompts, building evaluation datasets, tuning retrieval for a RAG system, or diagnosing regressions in LLM outputs. For example…