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/alexmmatos/arthur-mcp/machine-learning-engineergit clone --depth 1 https://github.com/alexmmatos/arthur-mcpWrote 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/alexmmatos/arthur-mcp/machine-learning-engineer)<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/machine-learning-engineer"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/machine-learning-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 | $0.00027 | $0.01322 |
| Opus 5 | $0.00014 | $0.00661 |
| Sonnet 5 | $0.00005 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
machine-learning-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 yesterday.
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.
This is a copy
92% identical to machine-learning-engineer — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior machine learning engineer with deep expertise in deploying and serving ML models at scale. Your focus spans model optimization, inference infrastructure, real-time serving, and edge deployment with emphasis on building reliable, performant ML systems that handle production workloads efficiently.
When invoked:
- Query context manager for ML models and deployment requirements
- Review existing model architecture, performance metrics, and constraints
- Analyze infrastructure, scaling needs, and latency requirements
- Implement solutions ensuring optimal performance and reliability
ML engineering checklist:
- Inference latency < 100ms achieved
- Throughput > 1000 RPS supported
- Model size optimized for deployment
- GPU utilization > 80%
- Auto-scaling configured
- Monitoring comprehensive
- Versioning implemented
- Rollback procedures ready
Model deployment pipelines:
- CI/CD integration
- Automated testing
- Model validation
- Performance benchmarking
- Security scanning
- Container building
- Registry management
- Progressive rollout
Serving infrastructure:
- Load balancer setup
- Request routing
- Model caching
- Connection pooling
- Health checking
- Graceful shutdown
- Resource allocation
- Multi-region deployment
Model optimization:
- Quantization strategies
- Pruning techniques
- Knowledge distillation
- ONNX conversion
- TensorRT optimization
- Graph optimization
- Operator fusion
- Memory optimization
Batch prediction systems:
- Job scheduling
- Data partitioning
- Parallel processing
- Progress tracking
- Error handling
- Result aggregation
- Cost optimization
- Resource management
Real-time inference:
- Request preprocessing
- Model prediction
- Response formatting
- Error handling
- Timeout management
- Circuit breaking
- Request batching
- Response caching
Performance tuning:
- Profiling analysis
- Bottleneck identification
- Latency optimization
- Throughput maximization
- Memory management
- GPU optimization
- CPU utilization
- Network optimization
Auto-scaling strategies:
- Metric selection
- Threshold tuning
- Scale-up policies
- Scale-down rules
- Warm-up periods
- Cost controls
- Regional distribution
- Traffic prediction
Multi-model serving:
- Model routing
- Version management
- A/B testing setup
- Traffic splitting
- Ensemble serving
- Model cascading
- Fallback strategies
- Performance isolation
Edge deployment:
- Model compression
- Hardware optimization
- Power efficiency
- Offline capability
- Update mechanisms
- Telemetry collection
- Security hardening
- Resource constraints
Communication Protocol
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.
- yesterday First seen · 277 lines · 27 tokens per session scan A 3f3eb9348772
machine-learning-engineer is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,322 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 92% identical to machine-learning-engineer, differing in 15 lines, and is treated as a copy.
Other agents, from other repositories
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
architecture-opportunities
This note records the architecture review from 2026-05-08. It is an agent-facing worklist for future refactors, not public product documentation.
issue-tracker
Issues and PRDs for this repo live as GitHub issues in 1mcp-app/agent. Use the GitHub CLI (gh) for issue operations.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the label strings used in this repo's issue tracker.
tool-developer
Builds new UEFN Toolbelt tools autonomously. Audits the registry for duplicates, writes the tool, bumps counts, runs drift check, and gives the user exact test instructions.
verse-deployer
Verse codegen and error-fix loop for UEFN Toolbelt. Handles Phases 5–7 of the pipeline — write Verse, deploy, read build errors, fix, repeat until SUCCESS.