Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/domfelipe/vibeflow-n8nnpx agentmods add skills/domfelipe/vibeflow-n8n/vibeflowWrote 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/domfelipe/vibeflow-n8n/vibeflow)<a href="https://agentmods.dev/skills/domfelipe/vibeflow-n8n/vibeflow"><img src="https://agentmods.dev/badge/skills/domfelipe/vibeflow-n8n/vibeflow/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/domfelipe/vibeflow-n8n/vibeflow"><img src="https://agentmods.dev/badge/skills/domfelipe/vibeflow-n8n/vibeflow.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.00083 | $0.00501 |
| Opus 5 | $0.00042 | $0.00251 |
| Sonnet 5 | $0.00017 | $0.00100 |
| Haiku 4.5 | $0.00008 | $0.00050 |
Grade A, and why
vibeflow 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 10d 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
Vibeflow
Use the CLI as the source of truth. Do not infer that a workflow is safe from its README, prompt, or visual layout.
Workflow
-
Locate the exported workflow JSON. Never inspect or mutate a live production workflow unless the user explicitly requests it.
-
Run Vibeflow from a repository checkout:
node bin/vibeflow.mjs check path/to/workflow.jsonFor a released version without a checkout:
npx --yes github:domfelipe/vibeflow-n8n#v0.9.0 check path/to/workflow.json -
Read references/policies.md when interpreting or repairing a finding.
-
Fix errors before warnings. Preserve credential references, expressions, node IDs, and unrelated workflow behavior.
-
Re-run the check after every repair. Stop only when blocking findings are gone or explicitly waived in
.vibeflow.jsonwith a documented reason. -
Report changed nodes, remaining warnings, and what still needs runtime validation in n8n.
Safety boundaries
- Never copy literal credentials into a workflow to silence
VF001. - Never disable
VF006for customer-facing agents without explicit user approval; an off switch must block inference and all AI responses. - Treat static analysis as a preflight, not proof of runtime correctness.
- Treat
VF010andVF011as outcome risks, even when the underlying node type is ordinary HTTP, database, or messaging. - Do not claim an outcome contract enforces runtime authorization, limits, audit durability, or recovery; verify those separately in the executing system.
- Prefer fixing a shared upstream node over duplicating guards across branches.
- Keep fixes local to the exported workflow until the user authorizes deployment.
Output
Return the CLI result, the smallest safe repair, and any unresolved runtime check. Use SARIF for GitHub code scanning and JSON for automation.
What ships with it
2 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.
- 10d ago First seen · 43 lines · 83 tokens per session scan A 5205cd7c7d8e
vibeflow is a skill published in the GitHub repository domfelipe/vibeflow-n8n (10 stars, last pushed 1mo ago), licensed MIT. It adds 83 tokens to every session and 501 once invoked, about $0.0004 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
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-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
minimal-fix
Produce the smallest possible code change that fixes a specific, well-scoped issue (CI failure, reviewer comment, typo). Use only when the fix target is explicit. Never refactor unrelated code.
loop-triage
Triage recent changes, CI failures, issues, and conversations. Produces a concise, actionable findings report suitable for a loop to consume. Writes structured output to a state file or Linear board.
ci-triage
Classify CI failures — distinguish clear regressions from infra flakes and security-test failures. Produces structured failure reports.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error.