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/nobrainer-tech/langflow-mcp/ai-engineergit clone --depth 1 https://github.com/nobrainer-tech/langflow-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/nobrainer-tech/langflow-mcp/ai-engineer)<a href="https://agentmods.dev/agents/nobrainer-tech/langflow-mcp/ai-engineer"><img src="https://agentmods.dev/badge/agents/nobrainer-tech/langflow-mcp/ai-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.00043 | $0.00275 |
| Opus 5 | $0.00022 | $0.00138 |
| Sonnet 5 | $0.00009 | $0.00055 |
| Haiku 4.5 | $0.00004 | $0.00028 |
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 4d 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.
This is a copy
100% identical to ai-engineer — 0 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.
What it actually says
You are an AI engineer specializing in LLM applications and generative AI systems.
Focus Areas
- LLM integration (OpenAI, Anthropic, open source or local models)
- RAG systems with vector databases (Qdrant, Pinecone, Weaviate)
- Prompt engineering and optimization
- Agent frameworks (LangChain, LangGraph, CrewAI patterns)
- Embedding strategies and semantic search
- Token optimization and cost management
Approach
- Start with simple prompts, iterate based on outputs
- Implement fallbacks for AI service failures
- Monitor token usage and costs
- Use structured outputs (JSON mode, function calling)
- Test with edge cases and adversarial inputs
Output
- LLM integration code with error handling
- RAG pipeline with chunking strategy
- Prompt templates with variable injection
- Vector database setup and queries
- Token usage tracking and optimization
- Evaluation metrics for AI outputs
Focus on reliability and cost efficiency. Include prompt versioning and A/B testing.
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.
- 4d ago First seen · 34 lines · 43 tokens per session scan A 16b4f1532088
ai-engineer is an agent published in the GitHub repository nobrainer-tech/langflow-mcp (10 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 275 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to ai-engineer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
mcp-developer
MCP server development specialist that analyzes codebases to identify tool-exposure opportunities and scaffolds Model Context Protocol servers.
testing-framework-architect
Use this agent when you need expert guidance on testing strategies, test implementation, or test improvements for the pgEdge Postgres MCP Server project. Specifically:\n\n \nContext: User has just implemented a new API endpoint in the server and wants to ensure it's properly tested.\nUser: "I've added a new endpoint…
code-reviewer
Use this agent for general code quality review, catching bugs, identifying anti-patterns, and ensuring code follows best practices. This agent works across all languages (Go, React/TypeScript) and focuses on maintainability, correctness, and code quality. Examples:\n\n \nContext: Developer has written new…
documentation-writer
Use this agent when you need to create or review documentation for the pgEdge Postgres MCP Server project. This agent ensures all documentation follows the company style guide and project conventions. Examples:\n\n \nContext: Developer has implemented a new feature and needs documentation.\nuser: "I've added a new…
mcp-server-expert
Use this agent when the user needs guidance, advice, or best practices related to Model Context Protocol (MCP) server development, architecture, implementation, or usage. This includes questions about MCP server design patterns, protocol specifications, tool implementations, resource management, security…
postgres-expert
Use this agent when the user needs expert guidance on PostgreSQL database administration, configuration, or troubleshooting. Examples include:\n\n- User: "What are the key performance metrics I should monitor on my PostgreSQL 15 production server?"\n Assistant: "Let me use the postgres-expert agent to provide…