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-custom-node-buildergit 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-custom-node-builder)<a href="https://agentmods.dev/skills/mohad44dsfasf/flowforge-n8n/n8n-custom-node-builder"><img src="https://agentmods.dev/badge/skills/mohad44dsfasf/flowforge-n8n/n8n-custom-node-builder/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-custom-node-builder"><img src="https://agentmods.dev/badge/skills/mohad44dsfasf/flowforge-n8n/n8n-custom-node-builder.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.00177 |
| Opus 5 | $0.00010 | $0.00088 |
| Sonnet 5 | $0.00004 | $0.00035 |
| Haiku 4.5 | $0.00002 | $0.00018 |
Grade A, and why
n8n-custom-node-builder 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 Custom Node Builder Skill
This skill outlines guidelines for packaging custom n8n integration nodes.
When to Use
Use when users want to generate TypeScript integrations, credentials types, or package assets matching n8n nodes templates.
Workflow Steps
- Define authentication mechanics (API Key vs OAuth2) and operations.
- Run
flowforge node-new <name> --auth <auth> --resource <resource> --operation <list>. - Fill in the code templates. Ensure class properties are lint-compliant.
Constraints
- Ensure all community naming structures begin with
n8n-nodes-. - Maintain clean typings and imports from
n8n-workflow.
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 · 21 lines · 21 tokens per session scan A 922b5e5a5cf5
n8n-custom-node-builder 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 177 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
work
Dispatch a tracker ticket into an isolated worktree and drive it autonomously to an open pull request, then stop for review. Pass interactive to brainstorm the ticket with a human before planning it, or a sentence of editorial direction as a rider. Use when asked to work a ticket end-to-end.
batch
Dispatch a night's batch of Todo tickets — one worktree and one pull request each — and leave a morning summary. Run explicitly; never inferred.
cleanup
Clean up after a merged pull request — return to the base branch, remove the worktree, delete the branch, sweep other stale branches and worktrees, and report tracker state. Use after a merge or whenever asked what is left over.
merge
Merge the reviewed pull request for the current branch, then hand straight off to cleanup. A sentence of editorial direction alongside the green light is read as a rider. Use when a human green-lights an open PR.
prep
Spec a ticket before it is dispatched. Brainstorms it, decides everything it can recommend an answer for, asks a present human about the little that survives, and leaves the spec, the decisions and anything still open as one ticket comment. No worktree, no branch, no pull request, and the ticket stays where it was.
plan-schema
Plan file (.claude/plans/-plan.md) reference — sections, per-file format, dependency graph, and converter mappings.