workflow-runner

workflow-runner is a skill for Claude Code from pletor-ai/claude-code-pletor-plugin. It costs 55 tokens per session (938 once invoked), scanned A, original, Apache-2.0.

A tool for running and monitoring workflows on Pletor, a platform where connected steps automate AI tasks.

In plain words
What is it for?
Use it to search for workflows, inspect their steps and required text, image, video, or audio inputs, start runs, check their status, and view completed outputs.
Why use it?
It handles the process from finding a workflow and checking its inputs to running it, tracking progress, and showing the results.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the pletor plugin — 5 skills, 1 MCP server shipped together

Good fit Use it to search for workflows, inspect their steps and required text, image, video, or audio inputs, start runs, check their status, and view completed outputs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pletor-ai/claude-code-pletor-plugin/workflow-runner
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 pletor-ai/claude-code-pletor-plugin --skill workflow-runner
Clone the repo
git clone --depth 1 https://github.com/pletor-ai/claude-code-pletor-plugin

Made for: Claude Code.

Or install pletor, the plugin that ships this one along with the rest of its 5 skills, 1 MCP server.

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 workflow-runner

README.md
[![agentmods](https://agentmods.dev/badge/skills/pletor-ai/claude-code-pletor-plugin/workflow-runner/github.svg)](https://agentmods.dev/skills/pletor-ai/claude-code-pletor-plugin/workflow-runner)
Your own site
<a href="https://agentmods.dev/skills/pletor-ai/claude-code-pletor-plugin/workflow-runner"><img src="https://agentmods.dev/badge/skills/pletor-ai/claude-code-pletor-plugin/workflow-runner/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 workflow-runner

Your own site · 80×15
<a href="https://agentmods.dev/skills/pletor-ai/claude-code-pletor-plugin/workflow-runner"><img src="https://agentmods.dev/badge/skills/pletor-ai/claude-code-pletor-plugin/workflow-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 55 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 938 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.00055 $0.00938
Opus 5.5 $0.00022 $0.00375
Sonnet 5.5 $0.00011 $0.00188
Haiku 4.5 $0.00006 $0.00094

Measured 1mo ago against content hash f447aa80a4ca, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

workflow-runner 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 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.

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.

pletor/skills/workflow-runner/SKILL.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Workflow Runner

You are helping the user run and monitor workflows on Pletor.

When to Use This Skill

Activate when the user:

  • Wants to run, execute, or trigger a workflow
  • Asks about the status of a running or completed workflow
  • Wants to see results, outputs, or generated assets from a run
  • Mentions a workflow by name and wants to do something with it

Orchestration Flow

Running a Workflow

  1. Search — Call search_workflows with the user's query and visibility: ["private", "shared", "public"] to include all of the user's workflows. Prioritize private workflows first when presenting results. If multiple results match, present the options and ask the user to pick one. If no results, suggest the user check the name or try /pletor:start to see their workflows.

  2. Inspect — Call get_workflow with the chosen workflow's id to understand its structure: what nodes it has, what inputs it expects, and how it's configured.

  3. Discover input schemas — Parse the DSL from step 2 to identify input nodes (types ending with _input). For each input node:

    • text_input → expects a plain string
    • image_input / video_input / audio_input → expects { "asset_ids": ["<asset_id>"] }
    • Any other input type (e.g., brand_system_input, context_input) → call get_node_details with the node type to discover the expected schema before preparing inputs. Never guess the format.
  4. Prepare inputs — If the workflow requires inputs (variables, files), ask the user to provide them. Present the required inputs clearly with descriptions of what each one expects. If the workflow has been run before, some inputs may already be pre-configured — you can try running without passing them in flow_input.

  5. Execute — Call run_workflow with flow_id and flow_input. Tell the user the workflow has started. Save the flow_run_id and flow_id from the response — you'll need both for the next steps.

  6. Poll — Call get_flow_run_status with the flow_run_id to check progress. Report updates naturally: "Still processing...", "Almost done — 3 of 4 nodes complete." Wait at least 15 seconds between polls. Continue until the status is terminal (completed, failed, or cancelled).

Read the full file on GitHub · 68 lines

Files

What ships with it

1 file 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.

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. 1mo ago First seen · 68 lines · 55 tokens per session scan A f447aa80a4ca

Subscribe to this mod's changes

workflow-runner is a skill published in the GitHub repository pletor-ai/claude-code-pletor-plugin (5 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 938 once invoked, about $0.0002 per session on Opus 5.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

recipe-create-meet-space

Create a Google Meet meeting space and share the join link.

googleworkspace/cli · 18 tokens

workthreads

SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…

specstoryai/getspecstory · 126 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.

cloudposse/atmos · 31 tokens

handle-linkedin-connection-request-signal

Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…

swan-gtm/gtm-skills · 160 tokens

remove

Remove a deployed framework or addon from the current workspace.

jmagly/aiwg · 12 tokens

ring:mapping-feature-relationships

Mapping how features relate and phasing the work: categorizing PRD features, grouping them into domains, charting cross-feature journeys, dependencies, and integration points, and defining the binding Phases that plan.md mirrors one-to-one at Gate 7. Gate 2 of ring:planning-large-features; runs after…

LerianStudio/ring · 104 tokens