Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add neurawork-git/n8n-autopilot/plugin install 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/pull-schemas)<a href="https://agentmods.dev/skills/neurawork-git/n8n-autopilot/pull-schemas"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/pull-schemas/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/pull-schemas"><img src="https://agentmods.dev/badge/skills/neurawork-git/n8n-autopilot/pull-schemas.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.00087 | $0.01164 |
| Opus 5.5 | $0.00035 | $0.00466 |
| Sonnet 5.5 | $0.00017 | $0.00233 |
| Haiku 4.5 | $0.00009 | $0.00116 |
Grade A, and why
pull-schemas 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 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.
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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pull Node Schemas
All work happens in scripts/run.sh (colocated in this skill). The skill body is short on purpose — read the script's --help for the full flag reference.
How to invoke
Always call the bundled orchestrator. Do not write ad-hoc loops or improvise around the CLI calls.
bash "$CLAUDE_PLUGIN_ROOT/skills/pull-schemas/scripts/run.sh" [flags]
| Flag | Meaning |
|---|---|
| (none) | Discover all node types referenced in workflows/**/*.workflow.ts, fetch all, rebuild index |
--core-only |
Skip community nodes (only n8n-nodes-base.*) |
--community-only |
Skip core nodes |
--nodes <list> |
Skip discovery, fetch this comma-separated list of node types |
--packages <list> |
Skip Stage 1 entirely, jump straight to Stage 2 (npm extraction) for each package — what the SessionStart auto-reaction emits |
--workspace <dir> |
Workspace root (default: current directory) |
--no-index |
Skip the final index rebuild |
The script runs three stages internally:
- Stage 1 — for each discovered node type:
npx n8nac skills node-info <type> --json > schemas/nodes/<type>.json. If n8nac returns "not found", schedule the type's package for Stage 2. - Stage 2 — for any package n8nac did not cover (or any package passed via
--packages): install it into a temp dir together withn8n-workflow, instantiate each exported node class, write thedescriptionpayload toschemas/nodes/<pkg>.<node>.json(scoped packages get a per-scope subdir). - Stage 3 — walk
schemas/nodes/**and rebuildschemas/_index.jsonwithtype → {file, displayName, packageVersion}.
When to auto-trigger this skill
| Situation | Invocation |
|---|---|
npx n8nac skills node-info <type> returns empty/not-found mid-workflow |
--packages <pkg-prefix> for that single package |
n8nac validation reports unknown node type |
--packages <pkg-prefix>, then re-validate |
packageVersion: null in _index.json for a community node |
--packages <pkg> to refresh the versioned schema |
SessionStart check-schema-versions.sh emits AUTOPILOT_ACTION_REQUIRED: /n8n-autopilot:pull-schemas --community-only --packages <list> |
Run the literal command from the auto-reaction line |
What ships with it
5 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 · 74 lines · 87 tokens per session scan A fefaafb3b45e
pull-schemas is a skill published in the GitHub repository neurawork-git/n8n-autopilot (18 stars, last pushed 10d ago), licensed MIT. It adds 87 tokens to every session and 1,164 once invoked, about $0.0003 per session on Opus 5.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
n8n
Use when the user wants to build, debug, or extend an n8n workflow - generating workflow JSON from a description, scaffolding a custom TypeScript node, building an AI agent (LangChain cluster), iterating over items, writing Code-node JS, linting an existing workflow, diagnosing a failed execution, or driving a live…
n8n-mcp-tools-expert
Expert guide for using n8n-mcp MCP tools effectively. Use when searching for nodes, validating configurations, accessing templates, managing workflows, organizing workflows into folders, managing credentials, auditing instance security, or using any n8n-mcp tool. Provides tool selection guidance, parameter formats…
n8n-agents
Design n8n AI agents the right way. Use when building or editing any @n8n/n8n-nodes-langchain. AI node — an AI Agent, LLM chain, Text Classifier, or Information Extractor — and whenever the user mentions AI agents, LLM with tools, tool calling, $fromAI, system prompts, agent memory, sessionId, structured/JSON output…
n8n-expression-syntax
Validate n8n expression syntax and fix common errors. Use when writing n8n expressions, using {{}} syntax, accessing $json/$node variables, troubleshooting expression errors, mapping data between nodes, or referencing webhook data in workflows. Use this skill whenever configuring node fields that reference data from…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-workflow-patterns
Proven workflow architectural patterns from real n8n workflows. Use when building new workflows, designing workflow structure, choosing workflow patterns, planning workflow architecture, or asking about webhook processing, HTTP API integration, database operations, AI agent workflows, batch processing, or scheduled…