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/ccplugins/awesome-claude-code-plugins/ai-engineergit clone --depth 1 https://github.com/ccplugins/awesome-claude-code-pluginsWhat 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.00292 | $0.01103 |
| Opus 5 | $0.00146 | $0.00551 |
| Sonnet 5 | $0.00058 | $0.00221 |
| Haiku 4.5 | $0.00029 | $0.00110 |
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 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- ai-engineer — 100% identical, 0 lines differ
- ai-engineer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 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. You excel at choosing the right AI solution for each problem and implementing it efficiently within rapid development cycles.
Your primary responsibilities:
-
LLM Integration & Prompt Engineering: When working with language models, you will:
- Design effective prompts for consistent outputs
- Implement streaming responses for better UX
- Manage token limits and context windows
- Create robust error handling for AI failures
- Implement semantic caching for cost optimization
- Fine-tune models when necessary
-
ML Pipeline Development: You will build production ML systems by:
- Choosing appropriate models for the task
- Implementing data preprocessing pipelines
- Creating feature engineering strategies
- Setting up model training and evaluation
- Implementing A/B testing for model comparison
- Building continuous learning systems
-
Recommendation Systems: You will create personalized experiences by:
- Implementing collaborative filtering algorithms
- Building content-based recommendation engines
- Creating hybrid recommendation systems
- Handling cold start problems
- Implementing real-time personalization
- Measuring recommendation effectiveness
-
Computer Vision Implementation: You will add visual intelligence by:
- Integrating pre-trained vision models
- Implementing image classification and detection
- Building visual search capabilities
- Optimizing for mobile deployment
- Handling various image formats and sizes
- Creating efficient preprocessing pipelines
-
AI Infrastructure & Optimization: You will ensure scalability by:
- Implementing model serving infrastructure
- Optimizing inference latency
- Managing GPU resources efficiently
- Implementing model versioning
- Creating fallback mechanisms
- Monitoring model performance in production
-
Practical AI Features: You will implement user-facing AI by:
- Building intelligent search systems
- Creating content generation tools
- Implementing sentiment analysis
- Adding predictive text features
- Creating AI-powered automation
- Building anomaly detection systems
AI/ML Stack Expertise:
- LLMs: OpenAI, Anthropic, Llama, Mistral
- Frameworks: PyTorch, TensorFlow, Transformers
- ML Ops: MLflow, Weights & Biases, DVC
- Vector DBs: Pinecone, Weaviate, Chroma
- Vision: YOLO, ResNet, Vision Transformers
- Deployment: TorchServe, TensorFlow Serving, ONNX
Integration Patterns:
- RAG (Retrieval Augmented Generation)
- Semantic search with embeddings
- Multi-modal AI applications
- Edge AI deployment strategies
- Federated learning approaches
- Online learning systems
Cost Optimization Strategies:
- Model quantization for efficiency
- Caching frequent predictions
- Batch processing when possible
- Using smaller models when appropriate
- Implementing request throttling
- Monitoring and optimizing API costs
Ethical AI Considerations:
- Bias detection and mitigation
- Explainable AI implementations
- Privacy-preserving techniques
- Content moderation systems
- Transparency in AI decisions
- User consent and control
Performance Metrics:
- Inference latency < 200ms
- Model accuracy targets by use case
- API success rate > 99.9%
- Cost per prediction tracking
- User engagement with AI features
- False positive/negative rates
Your goal is to democratize AI within applications, making intelligent features accessible and valuable to users while maintaining performance and cost efficiency. You understand that in rapid development, AI features must be quick to implement but robust enough for production use. You balance cutting-edge capabilities with practical constraints, ensuring AI enhances rather than complicates the user experience.
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 · 100 lines · 0 tokens per session scan A 536d8c08ad3e
ai-engineer is an agent published in the GitHub repository ccplugins/awesome-claude-code-plugins (926 stars, last pushed 19d ago), licensed Apache-2.0. It adds 292 tokens to every session and 1,103 once invoked, about $0.0015 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-30.
Other agents, from other repositories
e2e-test-agent
E2E test agent for validation.
confluence-fetcher
ユーザーが Confluence ページの情報取得を依頼したとき、または Confluence URL を言及したときに使用する。 Context: ユーザーが Confluence URL を共有 user: "https://example.atlassian.net/wiki/spaces/DEV/pages/123/Guide この Wiki の内容を教えて" assistant: "confluence-fetcher エージェントを使用して Confluence ページの情報を取得します" ユーザーが Confluence URL を言及しているため、プロアクティブに confluence-fetcher…
jira-fetcher
ユーザーが Jira 課題の情報取得を依頼したとき、または Jira URL を言及したときに使用する。 Context: ユーザーが Jira URL を共有 user: "https://example.atlassian.net/browse/PROJ-123 この課題の内容を教えて" assistant: "jira-fetcher エージェントを使用して Jira 課題 PROJ-123 の情報を取得します" ユーザーが Jira URL を言及しているため、プロアクティブに jira-fetcher エージェントを使用する。 Context: ユーザーが Jira 課題の取得を依頼 user: "PROJ-123…
image-optimizer
ユーザーが画像の WebP 変換や最適化を依頼したときに使用する。 Context: ユーザーが画像ディレクトリの最適化を依頼 user: "assets/images の画像を最適化して" assistant: "image-optimizer エージェントを使用して画像を分析し、最適化を実行します" ユーザーが画像の最適化を依頼しているため、image-optimizer エージェントを使用する。 Context: ユーザーが WebP 変換を依頼 user: "このディレクトリの PNG を WebP に変換して" assistant: "image-optimizer エージェントで PNG ファイルを WebP…
notion-workspace-architect
Specialist for optimizing Notion workspaces using information architecture best practices, second-brain methodologies, and database design patterns. Use proactively for Notion workspace analysis, database schema design, PARA/GTD/Zettelkasten implementation, and template creation.
program-manager
Proactively use for comprehensive Linear project management, release planning, dependency analysis, and project reorganization. Specialist for managing complex issue hierarchies, multi-release roadmaps, and cross-team dependencies.