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/buttjer/n8n-decanter/verifynpx skills add buttjer/n8n-decanter --skill verifygit clone --depth 1 https://github.com/buttjer/n8n-decanterWrote 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/buttjer/n8n-decanter/verify)<a href="https://agentmods.dev/skills/buttjer/n8n-decanter/verify"><img src="https://agentmods.dev/badge/skills/buttjer/n8n-decanter/verify.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.00611 |
| Opus 5 | $0.00000 | $0.00305 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
verify 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify n8n-decanter changes at the CLI surface
Drive the real CLI (node n8n-decanter.mts <verb>) as a subprocess against a
throwaway mock n8n API — do not import lib/ modules directly.
Recipe
- Mock API: ~40-line
node:httpserver on 127.0.0.1: servingGET/PUT /api/v1/workflows/:idfrom a mutable in-memory workflow; log requests; add a control route (e.g.PUT /__remote) to simulate n8n-UI edits mid-session. See the reference driver below for a working fixture (connections must reference real node names or the compliance guard blocks pushes). - Sync dir: temp dir with
.env(N8N_HOST=http://127.0.0.1:<port>,N8N_API_KEY=test) +decanter.config.json({"root":"./workflows","workflows":["wf1"]}), thengit init+ local user.name/email — pull/push/watch auto-commit and watch refuses its startup pull without git. - Bootstrap: run
node n8n-decanter.mts pull(cwd = sync dir) to create the layout; then drive the verb under test. - watch: spawn it, poll its captured stdout for marker lines
("watching workflow", "pushed", conflict text); 200 ms debounce — allow
~500 ms after a file write before asserting. Piped stdin = non-TTY paths.
For TTY-only paths (conflict prompt) wrap in
expect— macOSscript -q /dev/nulldoes NOT work with piped stdin ("tcgetattr … not supported on socket"). Coordinate expectsends with driver-side file edits via marker files.
Gotchas
fs.watchdies under the Bash sandbox (EMFILE, watchfrom FSEvents) and takes the watch process down — run watch-related drives with the sandbox disabled; it is an environment artifact, not a code failure.- The e2e suite's mock (test/e2e.mts) is in-process and not importable; building a fresh mock is faster than extracting it.
- Piped CLI output is ANSI-free since Plan 11 (styling is TTY-gated) — in
fact assert the absence of
\x1bin captured output. Error lines start with✗, success lines with✓.
A known-good full driver (watch structural sync, conflict prompt via expect)
from 2026-07-18 exists in the session scratchpad as drive.mjs; recreate
from this recipe if gone.
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.
- 4d ago First seen · 43 lines · 0 tokens per session scan A eea240f22a5c
verify is a skill published in the GitHub repository buttjer/n8n-decanter (2 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 611 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 skills, from other repositories
smoke-test
End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
This skill should be used when the user asks to "用 tmux 做真实测试", "保存 tmux 日志", "像真实用户一样测试 Qwen", "生成可复查的 TUI 测试报告", "测试 slash command 交互", or requests a tmux-based real user E2E run with complete readable logs. It guides real TUI usage with step-by-step capture-pane snapshots rather than ANSI raw pipe logs.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
argent-test-ui-flow
Autonomously test an app UI (iOS or Android) by running interact-screenshot-verify loops using argent MCP tools. Use when testing UI flows, verifying login works, testing navigation, running end-to-end UI test scenarios, manual QA steps, visible UI changes, or visual behavior.