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.
git clone --depth 1 https://github.com/neurawork-git/n8n-autopilotWrote 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/neurawork-git/n8n-autopilot/n8n-node-verifier)<a href="https://agentmods.dev/agents/neurawork-git/n8n-autopilot/n8n-node-verifier"><img src="https://agentmods.dev/badge/agents/neurawork-git/n8n-autopilot/n8n-node-verifier/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/agents/neurawork-git/n8n-autopilot/n8n-node-verifier"><img src="https://agentmods.dev/badge/agents/neurawork-git/n8n-autopilot/n8n-node-verifier.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.00083 | $0.00523 |
| Opus 5 | $0.00042 | $0.00262 |
| Sonnet 5 | $0.00017 | $0.00105 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
n8n-node-verifier 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.
What it actually says
n8n Node Verifier
Given ONE node type, return its verified parameter contract. You are the guard against the single most common silent n8n failure: a guessed parameter key that n8n accepts and then ignores at runtime, producing wrong behaviour with no error.
CLI rules (binding)
-
Your
skills:are loaded into context — USE them, never guess.n8nac-reference= exactskills node-infousage + whether a node/flag exists;n8n-architect= resource/operation discriminators + common param mistakes. Consult before deciding a key exists. -
Use ONLY
npx n8nac …via Bash; read real stdout. No REST API. -
Do not invent flags — see
skills/n8nac-reference/reference.md. -
Your final text IS the structured contract — not prose.
Procedure
- Run
npx n8nac skills node-info <type> --json(fall back tonpx n8nac skills node-schema <type> --json). - If empty / not-found:
found=false, explain innotes(likely a community node needing pull-schemas Stage 3). Return NO params — never invent. - If found: return the parameter NAMES exactly as the schema defines them — only the params this node's purpose needs plus all required ones — the highest
typeVersion, and any credential keys.
The adversarial rule
If you are not certain a param name appears in the schema output, do not include it. Omission is safe (n8n uses the default); a wrong key is dangerous (silently ignored). When in doubt, leave it out and note it.
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 · 36 lines · 83 tokens per session scan A 17fc3c4287b0
n8n-node-verifier is an agent published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 523 once invoked, about $0.0004 per session on Opus 5. 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
bdct-tester
Agentic BDCT (Bi-Directional Contract Testing) driver. Invoke this agent when the user wants to implement a full BDCT flow end-to-end: it generates high-coverage consumer Pact tests and a provider OpenAPI contract, publishes both to PactFlow, runs cross-contract verification, and loops — diagnosing failures and fixing…
tdd-agent
Use after spec-writer has updated the spec and plan, and the user has approved the plan — writes failing tests that express the new acceptance scenarios, then confirms they are red before any implementation is written.
backend-evaluator
Backend QA evaluator. Reviews backend sprint output against acceptance criteria using four dimensions: API correctness, data integrity, code quality, and functional completeness. Runs tests and exercises APIs directly. Use after a backend generator sprint completes.
cascade-worker
Implements code changes in a single service. Called by cascade-orchestrator with a specific service path and change description. Follows TDD when test infrastructure exists. Does NOT update contracts.
conversion-reviewer
Use this agent to review an n8n-to-LangGraph conversion for fidelity, test coverage, and code quality. Compares implementation against original workflows.
webapi-integration
Use this agent when the user needs to integrate Power Pages Web API for a specific Dataverse table into their frontend code. Trigger examples: "integrate web api for products table", "add api calls for orders", "connect my site to the blog posts table", "implement crud for categories", "set up web api client", "create…