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 masteranime/n8n-claude-skills --skill debug-workflowgit clone --depth 1 https://github.com/masteranime/n8n-claude-skillsWrote 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/masteranime/n8n-claude-skills/debug-workflow)<a href="https://agentmods.dev/skills/masteranime/n8n-claude-skills/debug-workflow"><img src="https://agentmods.dev/badge/skills/masteranime/n8n-claude-skills/debug-workflow/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/masteranime/n8n-claude-skills/debug-workflow"><img src="https://agentmods.dev/badge/skills/masteranime/n8n-claude-skills/debug-workflow.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.00145 | $0.01819 |
| Opus 5.5 | $0.00058 | $0.00728 |
| Sonnet 5.5 | $0.00029 | $0.00364 |
| Haiku 4.5 | $0.00015 | $0.00182 |
Grade A, and why
debug-workflow 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n Workflow Debugging
Fix n8n workflows the way a senior engineer does — systematically, not by guessing.
Triage: identify the failure class first
Ask the user (or infer from error text) which class:
| Class | Symptom | Common root causes |
|---|---|---|
| Expression error | Cannot read property X of undefined, red node badge |
Wrong expression syntax, missing = prefix, accessing undefined fields |
| Type mismatch | Expected string, got array, downstream weirdness |
Item Lists vs single item confusion, Split In Batches output shape |
| Silent empty | Workflow runs green but no output/side effect | Filter condition wrong, pinned stale data, credential scope |
| Auth failure | 401, 403, Invalid API key |
Wrong credential selected, expired token, OAuth refresh not configured |
| Rate limit | Intermittent 429, works manually, fails in batch | No backoff, batch too large, shared credential across workflows |
| Sub-workflow | Execute Workflow returns nothing or errors |
Parameters not passed, return value not set, wrong workflow ID |
Expression errors
The single biggest footgun: ={{ $json.field }} vs {{ $json.field }}. The leading = makes the field an expression. Without it, the literal string {{ $json.field }} is sent.
Check:
- Click the field — does it show the "expression" toggle (fx icon) highlighted? If not, it's literal mode.
- In code-view JSON, the value should start with
=:"value": "={{ $json.id }}"
Accessing undefined paths: $json.customer.email throws if customer is null. Use optional chaining: $json.customer?.email ?? 'unknown'.
Referencing earlier nodes: Use $('Node Name').item.json.field, NOT $node['Node Name'].json.field (deprecated). Quote exact node name including spaces.
Common expression patterns:
// Array access
{{ $json.items[0].name }}
{{ $json.items?.[0]?.name ?? 'empty' }}
// Previous node output
{{ $('Webhook').item.json.body.email }}
// All items from previous node (for loops)
{{ $('Split In Batches').all().map(i => i.json.id) }}
// Conditional
{{ $json.amount > 100 ? 'high' : 'low' }}
// Date formatting (n8n uses Luxon)
{{ $now.toISO() }}
{{ $now.minus({ days: 7 }).toFormat('yyyy-MM-dd') }}
// Environment vars (self-hosted)
{{ $env.MY_SECRET }}
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 · 138 lines · 145 tokens per session scan A c4370fec5e20
debug-workflow is a skill published in the GitHub repository masteranime/n8n-claude-skills (33 stars, last pushed 6mo ago), licensed MIT. It adds 145 tokens to every session and 1,819 once invoked, about $0.0006 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
refactor
Surgical code refactoring to improve maintainability without changing behaviour. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
moai-workflow-loop
Ralph Engine - Automated feedback loop with LSP diagnostics and AST-grep integration for continuous code quality improvement. Use when implementing error-driven development, automated fixing, or continuous quality validation workflows.
moai-workflow-testing
Use when writing tests, measuring coverage, or running characterization, performance, or PR-review QA. Comprehensive specialist combining DDD testing, characterization tests, performance profiling, and TRUST 5 quality-assurance validation.
langsmith-tracing
LangSmith tracing and debugging setup for LLM applications. Configure observability, capture traces, and enable debugging for LangChain/LangGraph agents.