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 skills add anatolykoptev/n8n-mcp-agent --skill test-workflowgit clone --depth 1 https://github.com/anatolykoptev/n8n-mcp-agentWrote 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/skills/anatolykoptev/n8n-mcp-agent/test-workflow)<a href="https://agentmods.dev/skills/anatolykoptev/n8n-mcp-agent/test-workflow"><img src="https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/test-workflow/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.
<a href="https://agentmods.dev/skills/anatolykoptev/n8n-mcp-agent/test-workflow"><img src="https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/test-workflow.svg" alt="Reviewed on agentmods" width="80" 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.00017 | $0.02836 |
| Opus 5.5 | $0.00007 | $0.01134 |
| Sonnet 5.5 | $0.00003 | $0.00567 |
| Haiku 4.5 | $0.00002 | $0.00284 |
Grade A, and why
test-workflow scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
│ curl .../workflows/<ID> │ How it starts
The opening of the file, as written. The whole thing — 352 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Workflow Skill
Universal testing solution for n8n workflows. Supports two patterns:
- Direct Webhook - for workflows with Webhook trigger
- Test Runner - for workflows with Execute Sub-workflow Trigger
Quick Start
1. Configure Environment
Create or update .env in the n8n-mcp-agent root:
N8N_URL=https://your-n8n-instance.com
N8N_API_KEY=your-api-key
TEST_RUNNER_PATH=test-runner # optional, default: test-runner
2. Setup Test Runner (one-time)
./scripts/setup-test-runner.sh
This creates a universal Test Runner workflow on your n8n instance.
3. Test Workflows
# Pattern 1: Direct webhook (for workflows with Webhook trigger)
./scripts/test-workflow.sh <workflow_id>
# Pattern 2: Test Runner (for workflows with Execute Sub-workflow Trigger)
./scripts/test-workflow.sh --runner <workflow_id>
Scripts
| Script | Purpose | When to Use |
|---|---|---|
setup-test-runner.sh |
Create Test Runner workflow | First time setup on new n8n instance |
test-workflow.sh |
Test any workflow | Always - main testing script |
add-subworkflow-trigger.sh |
Add testable trigger to workflow | If workflow has Manual/Schedule Trigger |
create-sample-workflow.sh |
Create sample testable workflow | For testing the setup |
AI Agent Decision Flow
User asks: "Test workflow <ID>"
│
▼
┌─────────────────────────────┐
│ 1. Get workflow details │
│ curl .../workflows/<ID> │
└─────────────┬───────────────┘
│
▼
┌─────────────────────────────┐
│ 2. Check trigger type │
└─────────────┬───────────────┘
│
┌─────────┴─────────┬────────────────┬──────────────────┐
│ │ │ │
▼ ▼ ▼ ▼
┌────────┐ ┌──────────────┐ ┌─────────────┐ ┌──────────────┐
│Webhook │ │ExecuteWorkflow│ │ManualTrigger│ │ScheduleTrigger│
│Trigger │ │Trigger │ │ │ │ │
└───┬────┘ └──────┬───────┘ └──────┬──────┘ └──────┬───────┘
│ │ │ │
▼ ▼ ▼ ▼
┌────────┐ ┌──────────────┐ ┌─────────────────────────────┐
│Pattern1│ │ Pattern 2 │ │ RUN: add-subworkflow- │
│Direct │ │ Test Runner │ │ trigger.sh <ID> │
└───┬────┘ └──────┬───────┘ │ Then use Pattern 2 │
│ │ └──────────────┬──────────────┘
▼ ▼ │
┌────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────┐
│ 3. Run test │
│ test-workflow.sh ... │
└─────────────────────────────┘
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 352 lines · 17 tokens per session scan A 7d0c08487144
test-workflow is a skill published in the GitHub repository anatolykoptev/n8n-mcp-agent (0 stars, last pushed 7mo ago), licensed MIT. It adds 17 tokens to every session and 2,836 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
field-test
Exercise tools, resources, and prompts against a live HTTP server via MCP JSON-RPC over curl. Starts the server, surfaces the catalog, runs real and adversarial inputs, measures every call (bytes, token estimate, wall-clock) and weighs the catalog, renders app tools' views in a headless MCP Apps host, and produces a…
agent-builder
Load immediately after an Agent intent, before the first agentbuilder call. Governs how you create, configure, test, and publish n8n Agents yourself with the agentbuilder tools: targeting, prerequisites, initial build, config freshness, interactive setup, models, memory, tools, and reply style. Use directly for…
n8n-workflows
Use when n8n workflow automation — nodes, triggers, expressions, credentials, webhooks, error handling. Use when working with n8n workflows.
plugin-testing
The ONLY supported way to test changes to the n8n-autopilot plugin itself: commit → push to the private repo → install FROM that repo → restart → verify registration. Use whenever a plugin change (agent, skill, hook, script) must be exercised in a real session. Hard rule: no cache hand-copying, no directory-pointer…