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/pletor-ai/claude-code-pletor-plugin/workflow-runnernpx skills add pletor-ai/claude-code-pletor-plugin --skill workflow-runnergit clone --depth 1 https://github.com/pletor-ai/claude-code-pletor-pluginWrote 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/pletor-ai/claude-code-pletor-plugin/workflow-runner)<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="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.00055 | $0.00938 |
| Opus 5 | $0.00028 | $0.00469 |
| Sonnet 5 | $0.00011 | $0.00188 |
| Haiku 4.5 | $0.00006 | $0.00094 |
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 3d 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 — 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
-
Search — Call
search_workflowswith the user's query andvisibility: ["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:startto see their workflows. -
Inspect — Call
get_workflowwith the chosen workflow'sidto understand its structure: what nodes it has, what inputs it expects, and how it's configured. -
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 stringimage_input/video_input/audio_input→ expects{ "asset_ids": ["<asset_id>"] }- Any other input type (e.g.,
brand_system_input,context_input) → callget_node_detailswith the node type to discover the expected schema before preparing inputs. Never guess the format.
-
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. -
Execute — Call
run_workflowwithflow_idandflow_input. Tell the user the workflow has started. Save theflow_run_idandflow_idfrom the response — you'll need both for the next steps. -
Poll — Call
get_flow_run_statuswith theflow_run_idto 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, orcancelled).
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.
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.
- 3d ago First seen · 68 lines · 55 tokens per session scan A f447aa80a4ca
workflow-runner is a skill published in the GitHub repository pletor-ai/claude-code-pletor-plugin (5 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 938 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…