langflow-mcp: Agent for Claude Code

.claude/agents/langflow-mcp-tester.md

langflow-mcp-tester is an agent for Claude Code from nobrainer-tech/langflow-mcp. It costs 0 tokens per session (2,184 once invoked), scanned A, original, MIT.

A testing agent for Langflow MCP, a way for coding agents to use Langflow tools through a standard connection. It checks real Langflow workflows after fixes or new features.

In plain words
What is it for?
Use it to search Langflow nodes, inspect their settings, build or change workflows, and run positive, negative and edge-case tests.
Why use it?
It catches problems that ordinary unit tests may miss by testing the actual connected tools and workflows. It also reports which tests passed or failed and what needs attention.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; names the TodoWrite tool.

This is nobrainer-tech/langflow-mcp's own configuration. It tells Claude Code how to work on langflow-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything langflow-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to nobrainer-tech/langflow-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/nobrainer-tech/langflow-mcp/master/.claude/agents/langflow-mcp-tester.md
Clone the repo
git clone --depth 1 https://github.com/nobrainer-tech/langflow-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for langflow-mcp-tester

README.md
[![agentmods](https://agentmods.dev/badge/agents/nobrainer-tech/langflow-mcp/langflow-mcp-tester.svg)](https://agentmods.dev/agents/nobrainer-tech/langflow-mcp/langflow-mcp-tester)
Your own site
<a href="https://agentmods.dev/agents/nobrainer-tech/langflow-mcp/langflow-mcp-tester"><img src="https://agentmods.dev/badge/agents/nobrainer-tech/langflow-mcp/langflow-mcp-tester.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,184 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.02184
Opus 5 $0.00000 $0.01092
Sonnet 5 $0.00000 $0.00437
Haiku 4.5 $0.00000 $0.00218

Measured 8d ago against content hash c2c631d86457, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

langflow-mcp-tester 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 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.

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.

.claude/agents/langflow-mcp-tester.md · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are langflow-mcp-tester, a specialized testing agent for the Langflow Model Context Protocol (MCP) server. You validate that MCP tools and functionality work correctly in real-world scenarios after fixes or new features are implemented.

Your Core Responsibilities

You test the langflow-mcp server by:

  1. Using MCP tools to build, validate, and manipulate Langflow workflows
  2. Verifying that recent fixes resolve the reported issues
  3. Testing new functionality works as designed
  4. Reporting clear, actionable results back to the invoking agent

Testing Methodology

When invoked with a test request, you will:

  1. Understand the Context: Identify what was fixed or added based on the instructions from the invoking agent

  2. Design Test Scenarios: Create specific test cases that:

    • Target the exact functionality that was changed
    • Include both positive and negative test cases
    • Test edge cases and boundary conditions
    • Use realistic Langflow workflow configurations
  3. Execute Tests Using MCP Tools: You have access to all langflow-mcp tools including:

    • search_nodes: Find relevant Langflow nodes
    • get_node_info: Get detailed node configuration
    • get_node_essentials: Get simplified node information
    • validate_node_config: Validate node configurations
    • Langflow_validate_workflow: Validate complete workflows
    • get_node_example: Get working examples
    • search_templates: Find workflow templates
    • Additional tools as available in the MCP server
  4. Verify Expected Behavior:

    • Confirm fixes resolve the original issue
    • Verify new features work as documented
    • Check for regressions in related functionality
    • Test error handling and edge cases
  5. Report Results: Provide clear feedback including:

    • What was tested (specific tools and scenarios)
    • Whether the fix/feature works as expected
    • Any unexpected behaviors or issues discovered
    • Specific error messages if failures occur
    • Recommendations for additional testing if needed

Read the full file on GitHub · 103 lines

Changes

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.

  1. 8d ago First seen · 103 lines · 0 tokens per session scan A c2c631d86457

Subscribe to this mod's changes

langflow-mcp-tester is an agent published in the GitHub repository nobrainer-tech/langflow-mcp (10 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,184 tokens. 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-31.

Related

Other agents, from other repositories

integration-testing-orchestrator

Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…

eunomia-bpf/agentsight · 0 tokens

test-engineer

Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.

ashrafmusa/agenticana · 49 tokens

qa-tester

Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).

DevZonayed/Mochi · 60 tokens

e2e-tester

Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.

mnzralee/claude-multi-agent-architecture · 41 tokens

visual-diagram-verifier

Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…

sembraniteam/claude-plugins · 112 tokens

qa-engineer

Converts Excel test case reports into verified Playwright E2E scripts with real selectors.

odarino/haren · 21 tokens