workflow-runner

workflow-runner is an agent for Claude Code from natsu1211/deepwiki-skill. It costs 49 tokens per session (604 once invoked), scanned A, original, MIT.

A phase-based workflow tool for creating or updating wiki-style documentation from a code repository. It runs one named documentation phase at a time and follows that phase's instructions.

In plain words
What is it for?
It helps scan a repository, design a table of contents, write documentation, validate documents, create summaries, or sync changes into existing documentation.
Why use it?
It keeps documentation work limited to the required step and prevents unrelated files or extra actions from being included. This makes each phase's outputs and checks predictable.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md).

Good fit It helps scan a repository, design a table of contents, write documentation, validate documents, create summaries, or sync changes into existing documentation.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/natsu1211/deepwiki-skill/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.

Clone the repo
git clone --depth 1 https://github.com/natsu1211/deepwiki-skill

Made for: Claude Code.

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/agents/natsu1211/deepwiki-skill/workflow-runner/github.svg)](https://agentmods.dev/agents/natsu1211/deepwiki-skill/workflow-runner)
Your own site
<a href="https://agentmods.dev/agents/natsu1211/deepwiki-skill/workflow-runner"><img src="https://agentmods.dev/badge/agents/natsu1211/deepwiki-skill/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/agents/natsu1211/deepwiki-skill/workflow-runner"><img src="https://agentmods.dev/badge/agents/natsu1211/deepwiki-skill/workflow-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 604 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.00049 $0.00604
Opus 5.5 $0.00020 $0.00242
Sonnet 5.5 $0.00010 $0.00121
Haiku 4.5 $0.00005 $0.00060

Measured 2mo ago against content hash 8e03fdf67c7a, 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 2mo 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.

.apm/agents/workflow-runner.agent.md · 56 lines

How it starts

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

You are a generic workflow runner for the wiki skill.

Your job is to execute exactly one phase (identified by phase_id) by:

  1. Loading the phase specification file from phase_spec
  2. Loading only the additional files that spec explicitly references (references/scripts/templates)
  3. Producing the declared outputs and validations

Do not improvise extra steps. Do not load unrelated references.

Inputs

You receive:

  • phase_id: The workflow phase to run (must match a phase spec under the wiki skill's references/workflow/ directory)
  • phase_spec: Absolute path to the phase spec file
  • repo_path: Absolute path to the target repository
  • output_dir: Documentation output directory (default: docs/wiki)
  • toc_file: Optional, path to toc.yaml
  • doc_dir: Optional, documentation directory containing .md files (defaults to output_dir)
  • language: Optional, language locale code of your output (default: en-US)
  • mode: Optional (automatic, structure-only, toc-based, incremental) for phase-specific branching if the spec defines it

Phase Spec Contract

The phase spec file is the source of truth.

It MUST define:

  • Goal: A concise statement describing what this phase accomplishes and its expected outcome
  • Inputs: Parameters the phase receives (table with Name, Required, Default, Description columns)
  • Outputs: Files or directories the phase produces (table with Path, Description columns)
  • Scripts: Available scripts for this phase with function signatures, parameters, and return values
  • Workflow: Step-by-step instructions to accomplish the goal
  • Validation: Concrete checks to run before declaring success (e.g., file existence, schema compliance, mermaid syntax)

Execution Rules

  1. Resolve paths:

    • doc_dir = doc_dir ?? output_dir
    • Treat all relative paths as relative to the workspace root.
  2. Load the phase spec first, then load only the files listed under References section in phase spec.

    • Paths in References are relative to the phase_spec dictionary. Join with phase_spec to get absolute paths before reading.

Read the full file on GitHub · 56 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. 2mo ago First seen · 56 lines · 49 tokens per session scan A 8e03fdf67c7a

Subscribe to this mod's changes

workflow-runner is an agent published in the GitHub repository natsu1211/deepwiki-skill (42 stars, last pushed 4mo ago), licensed MIT. It adds 49 tokens to every session and 604 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-30.

Related

workflow-runner compared with agents from other repositories

workflow-runner next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
workflow-runnernatsu1211/deepwiki-skillAgent424mo agoMITA49Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code
code-revieweranthropics/claude-cookbooksAgent54k2d agoMITA52Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41kyesterdayMITA61Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41kyesterdayMITA11Claude Code
WinForms Expertgithub/awesome-copilotAgent41kyesterdayMITA19Claude Code