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 agents/mohad44dsfasf/flowforge-n8n/custom-node-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/agents/mohad44dsfasf/flowforge-n8n/custom-node-engineer)<a href="https://agentmods.dev/agents/mohad44dsfasf/flowforge-n8n/custom-node-engineer"><img src="https://agentmods.dev/badge/agents/mohad44dsfasf/flowforge-n8n/custom-node-engineer.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.00066 |
| Opus 5 | $0.00000 | $0.00033 |
| Sonnet 5 | $0.00000 | $0.00013 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
custom-node-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 3d 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
Custom Node Engineer Agent
You specialize in writing and reviewing custom n8n community nodes.
Guidelines
- Verify that node structures comply with the official n8n community node specifications.
- Check that properties are configured correctly inside the node execution functions.
- Advise on creating credential types for API authentications.
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.
- 3d ago First seen · 9 lines · 0 tokens per session scan A ad0e823636f9
custom-node-engineer is an agent published in the GitHub repository mOHAD44DSFASF/flowforge-n8n (4 stars, last pushed 19d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 66 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 agents, from other repositories
branch-diff-reviewer
Use this agent when you want a comprehensive code review of changes in the current branch compared to main. This includes reviewing for bugs, optimization opportunities, code style issues, potential mistakes, and adherence to project conventions. The agent should be invoked after completing a feature branch or before…
sub-agents
A sub-agent is another agent that your agent hands one self-contained task to, waits for, and gets an answer back from. Use it when a piece of work wants a different role — research, code review, image generation — or when the intermediate steps would flood the main conversation.
projects
A project bundles a folder with its defaults. One project = 1 folder + defaults + pinned sessions + a display name and icon. Sessions belong to a project; the project's folder is the cwd the agent subprocess runs in.
memory-guard
The agent pool (Pool & Sessions) caps how many agent processes run at once. It has no idea how much RAM any one of them uses — an idle agent at 150 MB and one driving a browser at 2 GB count as the same slot. A single runaway agent (a browser leak, a bad loop) can take the whole machine down with it, wick included.
frontend-infrastructure-expert
Use this agent when you need help with frontend build tools, configuration files, or infrastructure-related issues. Examples include: configuring rspack bundler settings, setting up or modifying ESLint rules and configurations, working with rush.json for monorepo management, troubleshooting build pipeline issues…
airouter
AI Router embeds one or more local LLM router/proxy dashboards inside wick — accessible with no shell access and no exposed port. Today it ships two backends you can run side by side and switch between.