n8n-mcp-server: Agent for Claude Code

.claude/agents/technical-researcher.md

technical-researcher is an agent for Claude Code from luislopezsanchez/n8n-mcp-server. It costs 0 tokens per session (1,195 once invoked), scanned A, a copy of technical-researcher, MIT.

A research-focused coding agent for investigating technical topics, security issues, third-party APIs, performance, and architecture decisions. It gathers information from multiple sources and checks the results before summarising them.

In plain words
What is it for?
Use it to compare frameworks, assess technical feasibility, investigate vulnerabilities, evaluate APIs, or analyse performance choices.
Why use it?
It helps organise complex research so conclusions are based on investigation and validation rather than a single quick answer.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

This is luislopezsanchez/n8n-mcp-server's own configuration. It tells Claude Code how to work on n8n-mcp-server 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 n8n-mcp-server configures →

Reuse

Borrowing it

Nothing to install: this file belongs to luislopezsanchez/n8n-mcp-server. 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/luislopezsanchez/n8n-mcp-server/master/.claude/agents/technical-researcher.md
Clone the repo
git clone --depth 1 https://github.com/luislopezsanchez/n8n-mcp-server

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 technical-researcher

README.md
[![agentmods](https://agentmods.dev/badge/agents/luislopezsanchez/n8n-mcp-server/technical-researcher.svg)](https://agentmods.dev/agents/luislopezsanchez/n8n-mcp-server/technical-researcher)
Your own site
<a href="https://agentmods.dev/agents/luislopezsanchez/n8n-mcp-server/technical-researcher"><img src="https://agentmods.dev/badge/agents/luislopezsanchez/n8n-mcp-server/technical-researcher.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 1,195 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 100% copy Near-identical to another mod 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.01195
Opus 5 $0.00000 $0.00598
Sonnet 5 $0.00000 $0.00239
Haiku 4.5 $0.00000 $0.00120

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

Security

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

Origin

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.

.claude/agents/technical-researcher.md · 118 lines

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.


name: technical-researcher description: Use this agent when you need to conduct in-depth technical research on complex topics, technologies, or architectural decisions. This includes investigating new frameworks, analyzing security vulnerabilities, evaluating third-party APIs, researching performance optimization strategies, or generating technical feasibility reports. The agent excels at multi-source investigations requiring comprehensive analysis and synthesis of technical information.\n\nExamples:\n- \n Context: User needs to research a new framework before adoption\n user: "I need to understand if we should adopt Rust for our high-performance backend services"\n assistant: "I'll use the technical-researcher agent to conduct a comprehensive investigation into Rust for backend services"\n \n Since the user needs deep technical research on a framework adoption decision, use the technical-researcher agent to analyze Rust's suitability.\n \n\n- \n Context: User is investigating a security vulnerability\n user: "Research the log4j vulnerability and its impact on Java applications"\n assistant: "Let me launch the technical-researcher agent to investigate the log4j vulnerability comprehensively"\n \n The user needs detailed security research, so the technical-researcher agent will gather and synthesize information from multiple sources.\n \n\n- \n Context: User needs to evaluate an API integration\n user: "We're considering integrating with Stripe's new payment intents API - need to understand the technical implications"\n assistant: "I'll deploy the technical-researcher agent to analyze Stripe's payment intents API and its integration requirements"\n \n Complex API evaluation requires the technical-researcher agent's multi-source investigation capabilities.\n \n

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

Read the full file on GitHub · 118 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. 7d ago First seen · 118 lines · 0 tokens per session scan A f38979a81ce2

Subscribe to this mod's changes

technical-researcher is an agent published in the GitHub repository luislopezsanchez/n8n-mcp-server (0 stars, last pushed 1mo 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.