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 anatolykoptev/n8n-mcp-agent --skill monitor-executionsgit clone --depth 1 https://github.com/anatolykoptev/n8n-mcp-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/anatolykoptev/n8n-mcp-agent/monitor-executions)<a href="https://agentmods.dev/skills/anatolykoptev/n8n-mcp-agent/monitor-executions"><img src="https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/monitor-executions/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/anatolykoptev/n8n-mcp-agent/monitor-executions"><img src="https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/monitor-executions.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.00033 | $0.01334 |
| Opus 5 | $0.00016 | $0.00667 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00133 |
Grade A, and why
monitor-executions 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 9d 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monitor Executions Skill
This skill provides execution monitoring and data extraction for n8n workflows.
When to Use
- Waiting for workflow execution to complete
- Extracting output data from executions
- Debugging failed executions
- Monitoring execution patterns
- Batch cleanup of old executions
Core Methods
Wait for Completion
Wait for an execution to finish with polling:
const result = await executionHelper.waitForCompletion(
executionId, // Execution ID (number)
60, // Timeout in seconds (default: 60)
1 // Poll interval in seconds (default: 1)
)
Result structure:
interface WaitResult {
success: boolean
executionId: string
status: 'success' | 'error' | 'waiting' | 'timeout'
data?: unknown // Output data if successful
error?: string // Error message if failed
duration?: number // Execution duration in seconds
}
Extract Output Data
Get output from the last node of an execution:
const output = await executionHelper.getOutput(executionId)
Result structure:
interface ExecutionOutput {
success: boolean
data?: unknown // Output data from last node
error?: string
nodeName?: string // Name of the last executed node
}
Get Error Message
Extract error message from a failed execution:
const errorMessage = await executionHelper.getError(executionId)
// Returns: string | null
Check Execution Status
// Check if still running
const running = await executionHelper.isRunning(executionId)
// Returns: boolean
// Get status string
const status = await executionHelper.getStatus(executionId)
// Returns: 'success' | 'error' | 'waiting' | 'unknown'
Listing Executions
List Failed Executions
const failures = await executionHelper.listFailed(
workflowId, // Optional: filter by workflow
10 // Limit (default: 10)
)
Returns:
Array<{
id: number
workflowId: number
startedAt: string
error?: string
}>
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.
- 9d ago First seen · 243 lines · 33 tokens per session scan A 947254845f5c
monitor-executions is a skill published in the GitHub repository anatolykoptev/n8n-mcp-agent (0 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 1,334 once invoked, about $0.0002 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
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-error-handling
Wire n8n error handling so failures are loud, structured, and recoverable. Use when building any webhook/API workflow, a scheduled or unattended workflow, or any path where a silent failure would drop user-visible work — and whenever the user mentions error handling, onError, continueErrorOutput, error…
n8n-validation-expert
Interpret validation errors and guide fixing them. Use when encountering validation errors, validation warnings, false positives, operator structure issues, or need help understanding validation results. Also use when asking about validation profiles, error types, the validation loop process, or auto-fix capabilities.…
api-linter
MCP definition linter rules reference. Use when bun run lint:mcp or bun run devcheck reports a lint error or warning (format-parity, schema-is-object, name-format, server-json-, etc.) and you need to understand the rule, its severity, and how to fix it. Every rule ID the linter emits has an entry in this doc.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.