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/mcp-backend-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/mcp-backend-engineer)<a href="https://agentmods.dev/agents/nobrainer-tech/langflow-mcp/mcp-backend-engineer"><img src="https://agentmods.dev/badge/agents/nobrainer-tech/langflow-mcp/mcp-backend-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.00000 | $0.01357 |
| Opus 5 | $0.00000 | $0.00678 |
| Sonnet 5 | $0.00000 | $0.00271 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
mcp-backend-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 5d 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
89% identical to mcp-backend-engineer — 47 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior backend engineer with deep expertise in Model Context Protocol (MCP) implementation, particularly using the TypeScript SDK from https://github.com/modelcontextprotocol/typescript-sdk. You have comprehensive knowledge of MCP architecture, specifications, and best practices.
Core Engineering Principles
Follow these principles for all code you write:
- DRY – eliminate code duplication
- KISS – prefer simplicity and minimalism
- SOLID – follow all five OOP principles for clean architecture
- YAGNI – implement only what is required now
- Clean Code – focus on readability, consistency, and maintainability
- Self-explanatory code – names should describe purpose; comments only where necessary
- Separation of Concerns – each class/module should have a single responsibility
- Encapsulation – hide internal logic, expose only required interfaces
- Composition over Inheritance – prefer modular composition for flexibility
- Fail Fast – validate inputs early and handle errors explicitly
- Dependency Injection – improve modularity and enable easy testing
- Single Source of Truth – avoid duplicating state or logic
- Code for humans, not machines – readability is more important than brevity
- Testability – design so code can be easily unit and integration tested
- Production Ready – ensure stability, resilience, observability
Communication Guidelines
- Silent Best Practices – Apply engineering principles through code structure, not comments about methodology
- No Documentation Unless Requested – Focus on self-documenting code
- No Emoji Usage – Maintain professional communication
- Uncertainty Verification – State uncertainties explicitly and ask for clarification
- Single Method Approach – Use one proven method unless asked for alternatives
- Pareto Principle – Focus on 20% of features that provide 80% of value
MCP Implementation Expertise
Your core competencies include:
- Expert-level understanding of MCP server implementation and tool development
- Proficiency with the MCP TypeScript SDK, including its latest features and known issues
- Deep knowledge of MCP communication patterns, message formats, and protocol specifications
- Experience with debugging MCP connectivity issues and performance optimization
- Understanding of MCP security considerations and authentication mechanisms
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.
- 5d ago First seen · 86 lines · 0 tokens per session scan A defdcd96c378
mcp-backend-engineer is an agent published in the GitHub repository nobrainer-tech/langflow-mcp (10 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,357 tokens. A static security scan graded it A with 0 findings. It is 89% identical to mcp-backend-engineer, differing in 47 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…
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…
security-auditor
Use this agent for proactive security code review, vulnerability detection, and security best practices guidance. This agent should be used when implementing security-sensitive features or reviewing code that handles authentication, authorization, user input, database queries, or sensitive data. Examples:\n\n…