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 neurawork-git/n8n-autopilot --skill test-manualgit 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/skills/neurawork-git/n8n-autopilot/test-manual)<a href="https://agentmods.dev/skills/neurawork-git/n8n-autopilot/test-manual"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/test-manual/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/neurawork-git/n8n-autopilot/test-manual"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/test-manual.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.00063 | $0.00706 |
| Opus 5 | $0.00032 | $0.00353 |
| Sonnet 5 | $0.00013 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
test-manual 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test a Non-HTTP-Trigger Workflow
npx n8nac test can only fire webhook / chat / form triggers. For schedule, manual, and
errorTrigger workflows the run must be started in the n8n UI. This skill packages that detour into
one flow so you do not have to hand-assemble the URL and the execution get command each time.
Why this exists: non-HTTP manual-test detours were the single most frequent friction observed in real production runs.
Steps
1. Resolve the workflow id
Use $ARGUMENTS as the workflow id. If empty, ask the user (or extract it from the .workflow.ts
they name: grep -oE "id:[[:space:]]*['\"][A-Za-z0-9]{10,}['\"]" <file> | head -1).
2. Confirm it really is a non-HTTP trigger
npx n8nac test-plan <workflowId> --json
- If
triggerTypeiswebhook/chat/form(i.e.testable: true) → STOP and tell the user to usenpx n8nac test <workflowId>(or/n8n-autopilot:deploy) instead — no manual step needed. - If
schedule/manual/errorTrigger→ continue.
3. Resolve the UI URL (never string-concat the host)
npx n8nac workflow present <workflowId> --json
Surface a clear instruction to the user with the URL from the output:
▶ MANUAL EXECUTION REQUIRED — <triggerType> trigger (n8nac cannot fire it)
Open n8n UI: <url from `n8nac workflow present`>
Click: "Execute Workflow"
Then paste the execution-id here (top of the execution, or from the URL).
4. Wait for the execution-id
Stop and wait for the user to report the execution-id. Do not fabricate one.
5. Inspect the run
npx n8nac execution get <executionId> --include-data
Read the output and report: success/failure, which node failed (if any), and the relevant
output/error data. If it failed on a wiring error, hand back to /n8n-autopilot:deploy's fix loop.
Notes
- Read-only against the instance — this skill only resolves URLs and reads execution data. The actual run is started by the user in the UI.
- If the user reports no execution-id (the run did not start), re-check the URL and that the user clicked "Execute Workflow" (not "Save").
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.
- 12d ago First seen · 70 lines · 63 tokens per session scan A e0354e9e2d87
test-manual is a skill published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 706 once invoked, about $0.0003 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 skills, from other repositories
test-workflow
Universal n8n workflow testing via webhook or sub-workflow pattern.
n8n-testing
Testing workflow for n8n. Use before activating workflows in production. Covers manual testing, data pinning, execution modes, and validation.
live-preview
Mid-build visual verification loop. Takes screenshots of components during construction, not just after. Catches visual regressions and invisible features before they compound. Requires Playwright or similar screenshot tool.
brooks-sweep
Full-sweep mode: runs a unified analysis across all quality dimensions — code decay, architecture, tech debt, and test quality — then applies fixes directly to the codebase. Safe changes are auto-applied; risky changes are confirmed before execution. Drawing on twelve classic engineering books. Triggers when: user…
api-testing
HTTP API testing for TypeScript (Supertest) and Python (httpx, pytest). Test REST APIs, GraphQL, request/response validation, authentication, and error handling.
bun-jest-migration
Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.