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 ericrisco/rsc-harness --skill n8ngit clone --depth 1 https://github.com/ericrisco/rsc-harnessWrote 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/ericrisco/rsc-harness/n8n)<a href="https://agentmods.dev/skills/ericrisco/rsc-harness/n8n"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/n8n/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/ericrisco/rsc-harness/n8n"><img src="https://agentmods.dev/badge/skills/ericrisco/rsc-harness/n8n.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 64 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00099 | $0.02856 |
| Opus 5.5 | $0.00040 | $0.01142 |
| Sonnet 5.5 | $0.00020 | $0.00571 |
| Haiku 4.5 | $0.00010 | $0.00286 |
Grade B, and why
n8n scanned grade B with 2 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 1mo 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -sS -X POST "$N8N_API_URL/webhook-test/my-path" -H "Content-Type: application/json" -d '{"foo":"bar"}' Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
create → **validate** → test → **activate** → manage → delete. A concrete sketch per step, curl and How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
n8n — operate a live instance over its REST API and MCP
You already have a workflow design — the trigger→steps→error shape and the importable JSON, which is
automation-flows' job and this skill does not re-teach it. This skill is the operate half: push
that JSON into a running n8n, validate it, test it, flip it live, watch its executions, and tear it
down safely — all without touching the UI. n8n has the richest programmatic story of the no-code
platforms: a first-party REST API plus a mature MCP server, both hitting the same instance.
Connect first — REST API vs MCP
Two ways to drive the same instance. Pick by who is at the wheel.
| Public REST API | n8n-mcp (czlonkowski, de-facto standard) | |
|---|---|---|
| What it is | n8n's own HTTP API at {host}/api/v1 |
MCP server wrapping that API + offline node/expression knowledge |
| Best for | scripts, CI/CD, deterministic deploys, no extra dependency | an agent (Claude) building/fixing workflows in the loop — it can look up node schemas, then validate/autofix before it writes |
| Auth | API key in header X-N8N-API-KEY |
management tools need N8N_API_URL + N8N_API_KEY; node-knowledge tools need no auth |
| Surface | identical on self-host and *.app.n8n.cloud |
same underlying API; hosted trial at dashboard.n8n-mcp.com |
Version reality (verify at author time — n8n moves fast):
- API base is
{host}/api/v1. Self-host ships interactive Swagger at/api/v1/docs; cloud does not — on cloud, work from the docs. POST /workflows/{id}/execute(run-by-id) is recent (n8n PR #20234). Older instances lack it — there, the only programmatic run is POSTing to a Webhook node's URL.
.env
# host root only — you append /api/v1 for REST; n8n-mcp reads it whole
N8N_API_URL=https://your-instance.app.n8n.cloud # or N8N_HOST for self-host, e.g. http://localhost:5678
N8N_API_KEY=n8n_api_... # Settings → n8n API → Create an API key
What ships with it
5 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.
- 1mo ago First seen · 178 lines · 99 tokens per session scan B 4efac4d30422
n8n is a skill published in the GitHub repository ericrisco/rsc-harness (267 stars, last pushed 2d ago), licensed MIT. It adds 99 tokens to every session and 2,856 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
starting-a-new-project
Use when the workspace is empty, has no code, and the user brings a raw project idea. Normally reached via setting-up-a-project; not for an existing project.
file-a-task
File work into nohuman (taskadd) and check on it (taskstatus) via the nohuman MCP bridge, instead of doing the work inline.
no-code-automacao
Automações com Make (Integromat), Zapier, n8n e ActivePieces: criação de fluxos, integrações entre sistemas, automação de processos repetitivos e blueprints prontos para contexto brasileiro.
durable-work
Picks the board over sub-agents for cross-turn work.
ops-standup
Cross-repo morning briefing. Aggregation of recent commits, PRs, CI, blockers and priorities of the day. Trigger when the user wants a standup, an activity summary, or to know what happened.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.