n8n-mcp: Agent for Claude Code

.claude/agents/technical-researcher.md

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

A technical-research agent for investigating complex software questions and technology choices. It gathers information from several sources, checks their reliability, and turns the findings into an actionable report.

In plain words
What is it for?
It breaks questions into smaller topics, plans searches, compares technical options, evaluates sources, investigates vulnerabilities, and records citations.
Why use it?
It reduces the effort of researching unfamiliar tools, designs, APIs, security issues, and performance problems. Cross-checking sources helps separate dependable information from weak claims.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

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

About the project

n8n-MCP is a Model Context Protocol server that gives AI assistants structured knowledge of n8n's workflow-automation nodes, including their properties, operations, documentation, and examples. It helps developers use AI assistants to create and work with n8n workflows. The catalogue contains skills, agents, and instructions for using it.

czlonkowski/n8n-mcp · 22,855 stars · on GitHub · n8n-mcp.com

Reuse

Borrowing it

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/czlonkowski/n8n-mcp/technical-researcher/github.svg)](https://agentmods.dev/agents/czlonkowski/n8n-mcp/technical-researcher)
Your own site
<a href="https://agentmods.dev/agents/czlonkowski/n8n-mcp/technical-researcher"><img src="https://agentmods.dev/badge/agents/czlonkowski/n8n-mcp/technical-researcher/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for technical-researcher

Your own site · 80×15
<a href="https://agentmods.dev/agents/czlonkowski/n8n-mcp/technical-researcher"><img src="https://agentmods.dev/badge/agents/czlonkowski/n8n-mcp/technical-researcher.svg" alt="Reviewed on agentmods" width="80" 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 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.01195
Opus 5 $0.00000 $0.00598
Sonnet 5 $0.00000 $0.00239
Haiku 4.5 $0.00000 $0.00120

Measured 10d ago against content hash f38979a81ce2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, 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 10d 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

Copies of this mod

8 near-identical copies found in the catalogue:

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

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:

  1. Executive Summary (2-3 paragraphs)

    • Key findings and recommendations
    • Critical decision factors
    • Risk assessment
  2. Technical Overview

    • Core concepts and architecture
    • Key features and capabilities
    • Technical requirements and dependencies

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. 10d 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 czlonkowski/n8n-mcp (22,855 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.