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 commands/mohad44dsfasf/flowforge-n8n/flow-validategit 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/commands/mohad44dsfasf/flowforge-n8n/flow-validate)<a href="https://agentmods.dev/commands/mohad44dsfasf/flowforge-n8n/flow-validate"><img src="https://agentmods.dev/badge/commands/mohad44dsfasf/flowforge-n8n/flow-validate.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.00107 |
| Opus 5 | $0.00000 | $0.00053 |
| Sonnet 5 | $0.00000 | $0.00021 |
| Haiku 4.5 | $0.00000 | $0.00011 |
Grade A, and why
flow-validate 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 4d 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
Slash Command: /flow:validate
Purpose
Validate the syntax, schema, and connection integrity of an n8n workflow JSON file.
Execution Guide
flowforge validate <filepath>
To receive structured output, include the --json option:
flowforge validate <filepath> --json
Guidance
- Report duplicate node IDs, duplicate node names, or references to missing nodes.
- Clearly present warnings and schema errors. Do not ignore warning logs.
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.
- 4d ago First seen · 18 lines · 0 tokens per session scan A a606a5cc1ba8
flow-validate is a command published in the GitHub repository mOHAD44DSFASF/flowforge-n8n (4 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 107 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-08-31.
Other commands, from other repositories
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
save
Save this conversation as a new or existing reusable context.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.