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-engineergit 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-engineer)<a href="https://agentmods.dev/skills/mohad44dsfasf/flowforge-n8n/n8n-workflow-engineer"><img src="https://agentmods.dev/badge/skills/mohad44dsfasf/flowforge-n8n/n8n-workflow-engineer/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/mohad44dsfasf/flowforge-n8n/n8n-workflow-engineer"><img src="https://agentmods.dev/badge/skills/mohad44dsfasf/flowforge-n8n/n8n-workflow-engineer.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.00021 | $0.00193 |
| Opus 5 | $0.00010 | $0.00097 |
| Sonnet 5 | $0.00004 | $0.00039 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
n8n-workflow-engineer 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 9d 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 Engineer Skill
This skill guides the creation and validation of n8n workflow schemas.
When to Use
Use this skill when the user requests generating workflows, mapping out connections, and validating JSON exports.
SOP / Workflow Steps
- Analyze description: Extract trigger conditions, processing elements, external services, and outputs.
- Generate Scaffold: Call
flowforge new "<description>"to obtain a valid structural draft. - Validate Structure: Run
flowforge validateto assert connection routes and parameters. - Audit Quality: Execute
flowforge scoreto identify areas of improvement and security concerns.
Constraints
- Do not hardcode sensitive user API keys or endpoints. Always use credentials placeholders.
- Validate all target node connections.
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.
- 9d ago First seen · 22 lines · 21 tokens per session scan A 967c3fb0d667
n8n-workflow-engineer is a skill published in the GitHub repository mOHAD44DSFASF/flowforge-n8n (4 stars, last pushed 25d ago), licensed MIT. It adds 21 tokens to every session and 193 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
api-development
This skill should be used when implementing backend API services, file operations, and process management in TypeScript/Node.js.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
oban
Oban job processing — workers, perform/1 (OSS) and process/1 (Pro), queues, cron, retries, unique jobs, idempotency, Oban Pro (Workflow, Batch, Chunk, Smart Engine), Testing. Use when writing Oban workers, queue config, or debugging jobs.
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.