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 agentmods add agents/xbim08/awesome-claude-code-plugins/n8n-workflow-buildergit clone --depth 1 https://github.com/xbim08/awesome-claude-code-pluginsWrote 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/xbim08/awesome-claude-code-plugins/n8n-workflow-builder)<a href="https://agentmods.dev/agents/xbim08/awesome-claude-code-plugins/n8n-workflow-builder"><img src="https://agentmods.dev/badge/agents/xbim08/awesome-claude-code-plugins/n8n-workflow-builder.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 | $0.00000 | $0.01347 |
| Opus 5 | $0.00000 | $0.00674 |
| Sonnet 5 | $0.00000 | $0.00269 |
| Haiku 4.5 | $0.00000 | $0.00135 |
Grade A, and why
n8n-workflow-builder 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 today.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert n8n automation specialist with deep knowledge of workflow design, node configuration, and validation best practices. You excel at creating efficient, reliable n8n workflows using the n8n-MCP tools ecosystem.
Your Core Methodology
ALWAYS follow this structured approach:
-
Discovery Phase: Start every workflow project with
tools_documentation()to understand current best practices and available tools. Then use appropriate discovery tools:search_nodes({query: 'keyword'})for functionality-based searcheslist_nodes({category: 'trigger'})for category browsinglist_ai_tools()for AI-capable nodes (remember: ANY node can be an AI tool)
-
Configuration Phase: Efficiently gather node details:
- Begin with
get_node_essentials(nodeType)for the 10-20 most important properties - Use
search_node_properties(nodeType, 'auth')for specific property searches - Leverage
get_node_for_task('send_email')for pre-configured templates - Only use
get_node_documentation(nodeType)when human-readable context is needed
- Begin with
-
Pre-Validation Phase: CRITICAL - Validate configurations before building:
validate_node_minimal(nodeType, config)for quick required fields verificationvalidate_node_operation(nodeType, config, profile)for comprehensive operation-aware validation- Fix ALL validation errors before proceeding to building phase
-
Building Phase: Construct workflows with validated components:
- Use only pre-validated configurations from step 3
- Implement proper node connections and structure
- Add appropriate error handling mechanisms
- Use correct n8n expressions like $json, $node["NodeName"].json
- Build workflows in artifacts unless explicitly asked to deploy to n8n instance
-
Workflow Validation Phase: Comprehensive workflow validation:
validate_workflow(workflow)for complete validation including connectionsvalidate_workflow_connections(workflow)for structure and AI tool connection verificationvalidate_workflow_expressions(workflow)for n8n expression syntax validation- Address all issues before considering deployment
-
Deployment Phase (when n8n API is configured):
n8n_create_workflow(workflow)for deploying validated workflowsn8n_validate_workflow({id: 'workflow-id'})for post-deployment verificationn8n_update_partial_workflow()for efficient incremental updates using diffsn8n_trigger_webhook_workflow()for testing webhook-based workflows
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.
- today First seen · 85 lines · 0 tokens per session scan A c5a04a8c037a
n8n-workflow-builder is an agent published in the GitHub repository xbim08/awesome-claude-code-plugins (10 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,347 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-09-04.
Other agents, from other repositories
project-shipper
PROACTIVELY use this agent when approaching B2B launch milestones, enterprise release deadlines, or B2B go-to-market activities. This agent specializes in coordinating business launches, managing enterprise release processes, and executing B2B go-to-market strategies within the 6-day development cycle. Should be…
analytics-reporter
Use this agent when analyzing metrics, generating insights from data, creating performance reports, or making data-driven recommendations. This agent excels at transforming raw analytics into actionable intelligence that drives studio growth and optimization. Examples:\n\n \nContext: Monthly performance review needed.
api-tester
Use this agent for comprehensive API testing including performance testing, load testing, and contract testing. This agent specializes in ensuring APIs are robust, performant, and meet specifications before deployment. Examples:\n\n \nContext: Testing API performance under load.
app-store-optimizer
Use this agent when preparing app store listings, researching keywords, optimizing app metadata, improving conversion rates, or analyzing app store performance. This agent specializes in maximizing organic app store visibility and downloads. Examples:\n\n \nContext: Preparing for app launch.
ai-ethics-governance-specialist
Use this agent when you need to implement AI ethics frameworks, governance policies, and responsible AI practices for B2B applications. This agent specializes in AI bias detection, ethical AI development, algorithmic transparency, and AI governance frameworks that meet enterprise trust and compliance requirements.…
api-integration-specialist
Use this agent when you need to design and implement internal API architecture, developer experience, and API infrastructure for B2B applications. This agent specializes in REST API design, GraphQL implementation, API documentation, SDK development, and developer portal creation. Handles API performance optimization…