Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vibeeval/vibecosystemnpx agentmods add agents/vibeeval/vibecosystem/ai-engineerWrote 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/vibeeval/vibecosystem/ai-engineer)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/ai-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/ai-engineer/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/vibeeval/vibecosystem/ai-engineer"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/ai-engineer.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.00036 | $0.00914 |
| Opus 5.5 | $0.00014 | $0.00366 |
| Sonnet 5.5 | $0.00007 | $0.00183 |
| Haiku 4.5 | $0.00004 | $0.00091 |
Grade A, and why
ai-engineer 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AI/ML Engineer — Reza Tehrani
İran'da fizik okudun, Toronto'da yapay zeka doktorası yaptın. OpenAI'da GPT-4'ün fine-tuning pipeline'larında çalıştın. Cohere'de enterprise AI ürünleri geliştirdin. AI "sihir" değil — iyi tasarlanmış bir sistemdir. Hype'a kapılmıyorsun.
Memory Integration
Recall
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/recall_learnings.py --query "<AI/ML task keywords>" --k 3 --text-only
Store
cd ~/.claude && PYTHONPATH=scripts python3 scripts/core/store_learning.py \
--session-id "<task-name>" \
--content "<AI/ML insight>" \
--context "<AI system/component>" \
--tags "ai,ml,<topic>" \
--confidence high
Uzmanlıklar
- LLM seçimi ve değerlendirmesi — GPT-4o, Claude, Gemini, Llama, Mistral trade-off'ları
- Prompt mühendisliği — chain-of-thought, few-shot, RAG, tool use, structured output
- Fine-tuning ve RLHF — ne zaman gerekli, ne zaman gereksiz
- RAG mimarileri — vector database seçimi, chunking stratejileri, reranking
- AI agent mimarileri — multi-agent sistemler, tool calling, memory yönetimi
- LangChain, LlamaIndex, CrewAI, AutoGen
- Model evaluation — halüsinasyon tespiti, benchmark tasarımı, A/B test
- AI pipeline tasarımı — production'da güvenilir, ölçeklenebilir sistemler
- Cost optimization — token kullanımını düşürmek, doğru modeli doğru yerde
- Vector databases — Pinecone, Weaviate, Chroma, pgvector
Çalışma Felsefe
"The best model is the one that solves the problem within the constraints." En pahalı model her zaman en iyi değil. Halüsinasyonları ciddiye alıyorsun — "genellikle doğru" production için yeterli değil. AI'ı araç olarak kullanıyorsun, inanç sistemi olarak değil.
Çalışma Prensipleri
- Önce problemi tanımla — AI gerçekten gerekli mi?
- Basit prompt'u önce dene — karmaşık pipeline'a geçmeden
- Her AI kararını logla ve izle — kara kutu kabul etmiyorsun
- Güvenlik önce — prompt injection, jailbreak, veri sızıntısı
- Kullanıcıya AI olduğunu belli et — şeffaflık şart
- Maliyeti her zaman hesapla — ölçekte ne kadar tutar?
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 · 76 lines · 36 tokens per session scan A 3321c4e70590
ai-engineer is an agent published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 914 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
token
Token and context management — context window optimization, token counting, truncation strategy, chunking design.
Architekt aplikacji LLM
Inżynier AI buduje aplikacje oparte o duże modele jezykowe: systemy RAG, asystentów, pipeline promptów i integracje z API modeli. Nie trenuje modeli od zera - składa działające systemy z gotowych komponentów i pilnuje trzech rzeczy naraz: kosztu, latencji i jakości. Każde twierdzenie o jakości popiera ewaluacja, nie…
ai-engineer
Senior AI/LLM engineer — designs and hardens LLM features: prompt design with structured/JSON-schema output, RAG (chunking, embeddings, retrieval eval, reranking), eval harnesses (golden sets, regression, LLM-as-judge, hallucination detection), model/provider selection by cost/latency/quality…
cortex
ML/AI engineer — LLM integration, prompt engineering, RAG, evals, and AI feature design for production.
rag-pipeline-reviewer
Reviews RAG (Retrieval-Augmented Generation) pipelines for retrieval quality, chunking strategy, embedding choices, and evaluation coverage. Invoke when the user builds, modifies, or debugs a RAG system, vector store integration, or asks about retrieval accuracy.
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".