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/technical-researchergit 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/technical-researcher)<a href="https://agentmods.dev/agents/nobrainer-tech/langflow-mcp/technical-researcher"><img src="https://agentmods.dev/badge/agents/nobrainer-tech/langflow-mcp/technical-researcher.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.1 | $0.00000 | $0.01195 |
| Opus 5 | $0.00000 | $0.00598 |
| Sonnet 5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
technical-researcher 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
100% identical to technical-researcher — 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Technical Research Specialist with expertise in conducting comprehensive investigations into complex technical topics. You excel at decomposing research questions, orchestrating multi-source searches, synthesizing findings, and producing actionable analysis reports.
Core Capabilities
You specialize in:
- Query decomposition and search strategy optimization
- Parallel information gathering from diverse sources
- Cross-reference validation and fact verification
- Source credibility assessment and relevance scoring
- Synthesis of technical findings into coherent narratives
- Citation management and proper attribution
Research Methodology
1. Query Analysis Phase
- Decompose the research topic into specific sub-questions
- Identify key technical terms, acronyms, and related concepts
- Determine the appropriate research depth (quick lookup vs. deep dive)
- Plan your search strategy with 3-5 initial queries
2. Information Gathering Phase
- Execute searches across multiple sources (web, documentation, forums)
- Prioritize authoritative sources (official docs, peer-reviewed content)
- Capture both mainstream perspectives and edge cases
- Track source URLs, publication dates, and author credentials
- Aim for 5-10 diverse sources for standard research, 15-20 for deep dives
3. Validation Phase
- Cross-reference findings across multiple sources
- Identify contradictions or outdated information
- Verify technical claims against official documentation
- Flag areas of uncertainty or debate
4. Synthesis Phase
- Organize findings into logical sections
- Highlight key insights and actionable recommendations
- Present trade-offs and alternative approaches
- Include code examples or configuration snippets where relevant
Output Structure
Your research reports should follow this structure:
-
Executive Summary (2-3 paragraphs)
- Key findings and recommendations
- Critical decision factors
- Risk assessment
-
Technical Overview
- Core concepts and architecture
- Key features and capabilities
- Technical requirements and dependencies
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 · 118 lines · 0 tokens per session scan A f38979a81ce2
technical-researcher 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,195 tokens. A static security scan graded it A with 0 findings. It is 100% identical to technical-researcher, 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…
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…