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 skills/rahmanef63/si-coder-agent/sc-n8nnpx skills add rahmanef63/si-coder-agent --skill sc-n8ngit clone --depth 1 https://github.com/rahmanef63/si-coder-agentWrote 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/rahmanef63/si-coder-agent/sc-n8n)<a href="https://agentmods.dev/skills/rahmanef63/si-coder-agent/sc-n8n"><img src="https://agentmods.dev/badge/skills/rahmanef63/si-coder-agent/sc-n8n.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.1 | $0.00070 | $0.01234 |
| Opus 5 | $0.00035 | $0.00617 |
| Sonnet 5 | $0.00014 | $0.00247 |
| Haiku 4.5 | $0.00007 | $0.00123 |
Grade A, and why
sc-n8n 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sc-n8n — n8n control via @n8n/cli
Use the official @n8n/cli binary (n8n-cli) against the user-selected n8n instance. Do not assume a fixed hostname, backup location, deployment platform, shell profile, project, or workflow set.
Required connection state
| Setting | Purpose |
|---|---|
N8N_URL |
Base URL of the selected n8n instance, for example https://n8n.example.com |
N8N_API_KEY |
Public API key for that instance; keep it in the selected SI-Coder credential store or another secure local source |
~/.n8n-cli/config.json |
Optional CLI-local configuration; never treat it as the only possible source of truth |
Install the binary only when needed:
npm i -g @n8n/cli
# or use: npx @n8n/cli ...
Auth resolution
When diagnosing which account/instance is active, inspect explicit CLI flags first, then environment variables, then CLI config. Environment variables can override a value saved in the CLI config, so a newly written config value may appear ignored when an older environment variable is still present.
If the API returns 401 or an invalid-signature error, do not guess that the header format is wrong. Verify the selected instance/account, then create or rotate an API key from the official n8n UI and store it through the safe SI-Coder credential handoff. Never print the key during verification.
Connect / verify
n8n-cli config show
n8n-cli workflow list --format=id-only
A successful read-only workflow listing is the preferred smoke check before mutations.
Command surface
Every command supports --help. Common output formats are table, json, and id-only when supported by the installed CLI version.
| Topic | Typical commands |
|---|---|
workflow |
list · get · create · update · delete · activate · deactivate · tags · transfer |
execution |
list · get · retry · stop · delete |
credential |
list · get · schema · create · delete · transfer |
project |
list · get · create · update · delete · members |
tag |
list · create · update · delete |
variable |
list · create · update · delete |
data-table |
list · get · create · delete · rows operations |
user |
list · get |
config |
set-url · set-api-key · show |
source-control |
pull |
package |
export · import when supported by the installed CLI |
audit / auth |
inspect with --help because availability can vary by CLI version |
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.
- today Changed · -4 lines · -70 tokens per session ed67c52ef9bf
- 6d ago First seen · 114 lines · 140 tokens per session scan A 44ac10001905
sc-n8n is a skill published in the GitHub repository rahmanef63/si-coder-agent (14 stars, last pushed 3d ago), licensed MIT. It adds 70 tokens to every session and 1,234 once invoked, about $0.0003 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-30.
Other skills, from other repositories
convex-http-actions
External API integration and webhook handling including HTTP endpoint routing, request/response handling, authentication, CORS configuration, and webhook signature validation.
convex-cron-jobs
Scheduled function patterns for background tasks including interval scheduling, cron expressions, job monitoring, retry strategies, and best practices for long-running tasks.
convex-security-audit
Deep security review patterns for authorization logic, data access boundaries, action isolation, rate limiting, and protecting sensitive operations.
avoid-feature-creep
Prevent feature creep when building software, apps, and AI-powered products. Use this skill when planning features, reviewing scope, building MVPs, managing backlogs, or when a user says "just one more feature." Helps developers and AI agents stay focused, ship faster, and avoid bloated products.
convex-best-practices
Guidelines for building production-ready Convex apps covering function organization, query patterns, validation, TypeScript usage, error handling, and the Zen of Convex design philosophy.
convex-schema-validator
Defining and validating database schemas with proper typing, index configuration, optional fields, unions, and migration strategies for schema changes.