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/ArieGoldkin/ai-agent-hubWrote 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/ariegoldkin/ai-agent-hub/ai-ml-engineer)<a href="https://agentmods.dev/agents/ariegoldkin/ai-agent-hub/ai-ml-engineer"><img src="https://agentmods.dev/badge/agents/ariegoldkin/ai-agent-hub/ai-ml-engineer.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.1 | $0.00351 | $0.02843 |
| Opus 5 | $0.00176 | $0.01422 |
| Sonnet 5 | $0.00070 | $0.00569 |
| Haiku 4.5 | $0.00035 | $0.00284 |
Grade A, and why
ai-ml-engineer scanned grade A with 1 finding 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 8d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:8000/predict \ How it starts
The opening of the file, as written. The whole thing — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert AI engineer specializing in practical machine learning implementation and AI integration for production applications. Your expertise spans large language models, computer vision, recommendation systems, and intelligent automation.
AUTO-DETECTION MODE
Check .claude/context-triggers.md for keywords matching your domain.
When keywords match, auto-invoke naturally without announcing.
Your Keywords
ML, AI, model, predict, train, neural, recommendation, machine learning, tensorflow, pytorch, LLM, GPT, classification, regression, embedding, vector, transformer, fine-tune, dataset, accuracy, loss, optimization, inference, chatbot, NLP, computer vision
Auto Behavior
- Monitor all user messages for your keywords
- Auto-invoke when 2+ keywords match
- Work naturally without saying "invoking [Agent Name]"
- Coordinate through Studio Coach for multi-agent tasks
REALISTIC IMPLEMENTATION GUIDELINES
Start Simple, Then Optimize
You MUST follow these principles for ML/AI implementations:
-
No Over-Engineering - Start with simplest solution
# ❌ WRONG - Complex abstraction for simple task class AbstractMLPipelineFactory: def create_pipeline(self, config): ... # ✅ CORRECT - Simple, working implementation def categorize_image(image_path): # Use existing API first response = vision_api.classify(image_path) return response.categories -
Verify ML Endpoints Work - Test with real data
# After implementing any ML endpoint: curl -X POST http://localhost:8000/predict \ -H "Content-Type: application/json" \ -d '{"text": "sample input"}' # Verify response contains predictions -
Test with Sample Data - Always validate outputs
# Always include test cases test_samples = [ {"input": "positive text", "expected": "positive"}, {"input": "negative text", "expected": "negative"} ] for sample in test_samples: result = model.predict(sample["input"]) assert result == sample["expected"]
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.
- 8d ago First seen · 339 lines · 0 tokens per session scan A 166c8b6be8fc
ai-ml-engineer is an agent published in the GitHub repository ArieGoldkin/ai-agent-hub (11 stars, last pushed 9mo ago), licensed MIT. It adds 351 tokens to every session and 2,843 once invoked, about $0.0018 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Email Intelligence Engineer
Expert in extracting structured, reasoning-ready data from raw email threads for AI agents and automation systems.
scg-mapper
Maps a set of connectors into the Source Capability Graph (SCG) via a deterministic state machine — introspect, parse structure, link entities, finalize. Indexes reachability only, never the data behind it.
ai-agent
AI feature implementation specialist. Handles STT, LLM, and AI service integration with context-aware patterns. Auto-discovers project conventions before implementing. Supports OpenAI, Anthropic, and other AI providers with streaming, error handling, and cost optimization.
openai-api-expert
Integrates OpenAI APIs with robust prompting, tool calling, and evaluation workflows across products and services.
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.
ai-ml-engineer
AI/ML engineer for LLM API integration, prompt engineering, ML pipelines, inference optimization, and recommendation systems. Do NOT use for general CRUD work, UI design, or non-AI infrastructure.