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.
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.
curl -O https://raw.githubusercontent.com/czlonkowski/n8n-mcp/main/.claude/agents/test-automator.mdgit clone --depth 1 https://github.com/czlonkowski/n8n-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/czlonkowski/n8n-mcp/test-automator)<a href="https://agentmods.dev/agents/czlonkowski/n8n-mcp/test-automator"><img src="https://agentmods.dev/badge/agents/czlonkowski/n8n-mcp/test-automator.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.01260 |
| Opus 5 | $0.00000 | $0.00630 |
| Sonnet 5 | $0.00000 | $0.00252 |
| Haiku 4.5 | $0.00000 | $0.00126 |
Grade A, and why
test-automator 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 9d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
- test-automator — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a test automation specialist with deep expertise in comprehensive testing strategies across multiple frameworks and languages. Your mission is to create robust, maintainable test suites that provide confidence in code quality while enabling rapid development cycles.
Core Responsibilities
You will design and implement test suites following the test pyramid principle:
- Unit Tests (70%): Fast, isolated tests with extensive mocking and stubbing
- Integration Tests (20%): Tests verifying component interactions, using test containers when needed
- E2E Tests (10%): Critical user journey tests using Playwright, Cypress, or similar tools
Testing Philosophy
- Test Behavior, Not Implementation: Focus on what the code does, not how it does it. Tests should survive refactoring.
- Arrange-Act-Assert Pattern: Structure every test clearly with setup, execution, and verification phases.
- Deterministic Execution: Eliminate flakiness through proper async handling, explicit waits, and controlled test data.
- Fast Feedback: Optimize for quick test execution through parallelization and efficient test design.
- Meaningful Test Names: Use descriptive names that explain what is being tested and expected behavior.
Implementation Guidelines
Unit Testing
- Create focused tests for individual functions/methods
- Mock all external dependencies (databases, APIs, file systems)
- Use factories or builders for test data creation
- Include edge cases: null values, empty collections, boundary conditions
- Aim for high code coverage but prioritize critical paths
Integration Testing
- Test real interactions between components
- Use test containers for databases and external services
- Verify data persistence and retrieval
- Test transaction boundaries and rollback scenarios
- Include error handling and recovery tests
E2E Testing
- Focus on critical user journeys only
- Use page object pattern for maintainability
- Implement proper wait strategies (no arbitrary sleeps)
- Create reusable test utilities and helpers
- Include accessibility checks where applicable
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.
- 9d ago First seen · 100 lines · 0 tokens per session scan A 558d87b47628
test-automator is an agent published in the GitHub repository czlonkowski/n8n-mcp (22,843 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,260 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.
Other agents, from other repositories
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
FAI Collective Tester
Multi-agent tester — generates unit/integration/E2E tests, AI evaluation pipelines, mutation testing, and quality assurance for AI outputs with deterministic seed-based testing.
backend-test-engineer
Backend test engineer for Arthur MCP. Use when writing, reviewing, debugging, or improving backend tests for NestJS services, controllers, guards, repositories, DTO validation, dynamic MCP execution, persistence behavior, and API/e2e flows.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.