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 mOHAD44DSFASF/flowforge-n8n --skill n8n-workflow-debuggergit clone --depth 1 https://github.com/mOHAD44DSFASF/flowforge-n8nWrote 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/mohad44dsfasf/flowforge-n8n/n8n-workflow-debugger)<a href="https://agentmods.dev/skills/mohad44dsfasf/flowforge-n8n/n8n-workflow-debugger"><img src="https://agentmods.dev/badge/skills/mohad44dsfasf/flowforge-n8n/n8n-workflow-debugger.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.1 | $0.00021 | $0.00129 |
| Opus 5 | $0.00010 | $0.00064 |
| Sonnet 5 | $0.00004 | $0.00026 |
| Haiku 4.5 | $0.00002 | $0.00013 |
Grade A, and why
n8n-workflow-debugger 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 8d 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 Workflow Debugger Skill
Provides strategies for auditing, debugging, and fixing n8n workflow errors.
When to Use
Use when users report webhook validation issues, duplicate properties failures, or workflow node parameter syntax crashes.
Debugging Workflow
- Run
flowforge validateto detect duplicate keys or references to deleted nodes. - Run
flowforge lintto identify unconfigured retry/error strategies. - Check log details. Review conditional branch output indices.
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.
- 8d ago First seen · 17 lines · 21 tokens per session scan A c4c3b7ae6bd2
n8n-workflow-debugger is a skill published in the GitHub repository mOHAD44DSFASF/flowforge-n8n (4 stars, last pushed 24d ago), licensed MIT. It adds 21 tokens to every session and 129 once invoked, about $0.0001 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-31.
Other skills, from other repositories
review-loop
Run the adversarial verification loop — implement, then hand the change to a fresh checker that did not write it, fix what it finds, and re-dispatch until APPROVE. Use before claiming any behavioural change is done, and on requests like "review loop", "adversarial review", "independent review", "get this verified"…
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
perf
Analyze Elixir/Phoenix performance — N+1 queries, assign bloat, ecto optimization, genserver bottlenecks. Use when slowness, timeouts, or high memory reported.
trace
Trace Elixir call trees from entry points via mix xref. Use when debugging data flow, planning signature changes, or understanding how a bug reaches code.
compound-docs
Searchable Elixir/Phoenix/Ecto solution documentation system with YAML frontmatter. Builds institutional knowledge from solved problems. Use when consulting past solutions before investigating new issues.
retrospective-audit
Stage B of /prflow:retrospective-weekly: given a most-recent-first subset of one recurring pattern's occurrence-PR context bundles (bounded by auditbundlecap), re-derive the root cause and return one JSON object carrying a ranked findings array (one to three sub-patterns) — no edits, no worktree. Invoked as a subagent…