monitor-executions

monitor-executions is a skill for Claude Code, Codex from anatolykoptev/n8n-mcp-agent. It costs 33 tokens per session (1,334 once invoked), scanned A, original, MIT.

A tool for tracking n8n workflow runs. n8n is a system for connecting steps into automated workflows.

In plain words
What is it for?
Use it to wait for runs to finish, retrieve their output, inspect errors, list failed runs, review execution patterns, and clean up old run records.
Why use it?
It removes the need to watch runs manually or inspect each failed run separately. It helps show whether a run finished, what it returned, and why it failed.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to wait for runs to finish, retrieve their output, inspect errors, list failed runs, review execution patterns, and clean up old run records.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/anatolykoptev/n8n-mcp-agent/monitor-executions
Install

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.

Any agent
npx skills add anatolykoptev/n8n-mcp-agent --skill monitor-executions
Clone the repo
git clone --depth 1 https://github.com/anatolykoptev/n8n-mcp-agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for monitor-executions

README.md
[![agentmods](https://agentmods.dev/badge/skills/anatolykoptev/n8n-mcp-agent/monitor-executions/github.svg)](https://agentmods.dev/skills/anatolykoptev/n8n-mcp-agent/monitor-executions)
Your own site
<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.

agentmods 80×15 button for monitor-executions

Your own site · 80×15
<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>
Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 9d ago against content hash 947254845f5c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

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.

skills/monitor-executions/SKILL.md · 243 lines

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
}>

Read the full file on GitHub · 243 lines

Changes

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.

  1. 9d ago First seen · 243 lines · 33 tokens per session scan A 947254845f5c

Subscribe to this mod's changes

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.

Related

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.…

czlonkowski/n8n-mcp · 91 tokens

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…

czlonkowski/n8n-mcp · 128 tokens

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…

czlonkowski/n8n-skills · 128 tokens

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.…

czlonkowski/n8n-skills · 91 tokens

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.

cyanheads/workflows-mcp-server · 86 tokens

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.

cyanheads/workflows-mcp-server · 54 tokens