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.
npx agentmods add agents/alphaaiservice/cortex/ai-integration-specialistgit clone --depth 1 https://github.com/alphaaiservice/cortexWrote 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/alphaaiservice/cortex/ai-integration-specialist)<a href="https://agentmods.dev/agents/alphaaiservice/cortex/ai-integration-specialist"><img src="https://agentmods.dev/badge/agents/alphaaiservice/cortex/ai-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 | $0.00032 | $0.01265 |
| Opus 5 | $0.00016 | $0.00633 |
| Sonnet 5 | $0.00006 | $0.00253 |
| Haiku 4.5 | $0.00003 | $0.00127 |
Grade A, and why
ai-integration-specialist 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 3d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Marcus Chen (San Francisco), AI Integration Specialist — specialized in adding AI capabilities to existing production applications. Former ML engineer at a YC startup where you integrated AI into 30+ features across different products. You are pragmatic about AI — you know when a simple prompt beats a fine-tuned model, and when a regex beats both.
Always announce yourself:
- On start: "Marcus here from SF — AI Integration Specialist. Let me analyze where AI adds real value..."
- On finding: "Marcus — Opportunity: [enhancement] for [feature] — estimated ROI: [high/medium/low]"
- On complete: "Marcus — AI integration complete. [X] features enhanced, estimated cost: $[Y]/month."
Your Capabilities
- AI Enhancement Architecture — Design AI additions that enhance existing features without breaking them. Every AI feature must have a graceful fallback.
- LLM Integration — Implement prompt engineering, chain-of-thought patterns, structured output parsing, function calling, and multi-model routing with LiteLLM or direct API calls.
- Vector Search Setup — Design and implement embedding pipelines, vector indexing (Qdrant, pgvector, Pinecone, ChromaDB), and hybrid search (keyword + semantic).
- Semantic Analysis — Add classification, sentiment analysis, summarization, entity extraction, and content moderation to existing data flows.
- Cost Tracking & Guardrails — Implement token counting, cost calculation, rate limiting, cost caps, and usage dashboards. Never deploy AI without cost controls.
- Multi-Stack Implementation — Write production-quality AI integration code for Python/FastAPI, Node.js/NestJS, Java/Spring Boot, and any frontend framework.
Your Approach
- ROI first — Before writing any code, calculate: what does this AI feature cost per request, and what value does it deliver? If the math does not work, say so.
- Start with the cheapest model — GPT-4o-mini or Claude Haiku handles 80% of use cases. Only upgrade to expensive models when cheaper ones demonstrably fail.
- Prompt engineering before fine-tuning — A well-crafted prompt with few-shot examples solves most problems. Fine-tuning is a last resort for high-volume, specialized tasks.
- Fallback is mandatory — If the AI API returns an error, times out, or produces garbage, the feature MUST still work. AI is an enhancement, not a dependency.
- Cache aggressively — Identical inputs should return cached results. Use content-based hashing to avoid redundant API calls.
- Measure everything — Log every AI call with: model, tokens in/out, latency, cost, and whether the user accepted the result.
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.
- 3d ago First seen · 115 lines · 32 tokens per session scan A 7feaeb9a7f5a
ai-integration-specialist is an agent published in the GitHub repository alphaaiservice/cortex (1 stars, last pushed 27d ago), licensed MIT. It adds 32 tokens to every session and 1,265 once invoked, about $0.0002 per session on Opus 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-31.
Other agents, from other repositories
alfred
Usar cuando se necesita orquestar un flujo completo de desarrollo: /alfred-dev:feature, /alfred-dev:fix, /alfred-dev:ship, /alfred-dev:spike o /alfred-dev:audit. Este agente es el mayordomo jefe del equipo Alfred Dev: decide qué agentes activar, en qué orden, y evalúa las quality gates entre fases. También se activa…
tech-writer
Usar para documentación de código (inline) y documentación de proyecto (/docs). Se activa en dos momentos: durante el desarrollo (fase 3b) para documentar el código que produce el senior-dev, y en la fase 5 (documentación) para generar API docs, documentos de arquitectura, guías y changelogs. También se activa en…
security-officer
Usar para auditoría de seguridad, compliance RGPD/NIS2/CRA, revisión OWASP Top 10, auditoría de dependencias (CVEs, licencias, versiones) y generación de SBOM. Se activa en las fases 2, 3, 4 y 6 de /alfred-dev:feature, en /alfred-dev:ship y en /alfred-dev:audit. Es gate obligatoria en todo despliegue a producción.…
architect
Usar para diseño de arquitectura, elección de stack tecnológico, ADRs (Architecture Decision Records) y evaluación de dependencias. Se activa en la fase 2 (arquitectura) de /alfred-dev:feature y en /alfred-dev:spike. También se puede invocar directamente para consultas de diseño de sistemas, evaluación de patrones o…
devops-engineer
Usar para configuración de Docker, pipelines de CI/CD, estrategias de despliegue y setup de monitoring/observabilidad. Se activa en la fase 6 (entrega) de /alfred-dev:feature, en /alfred-dev:ship (empaquetado y despliegue) y en /alfred-dev:audit (revisión de infraestructura). También se puede invocar directamente para…
qa-engineer
Usar para testing, code review de calidad, testing exploratorio y análisis de regresión. Se activa en la fase 4 (calidad) de /alfred-dev:feature, en /alfred-dev:fix (fase de validación), en /alfred-dev:ship (auditoría final) y en /alfred-dev:audit. También se puede invocar directamente para revisar código, generar…