A workflow control skill for checking project contracts, planning their order, and launching selected work in separate Git worktrees. A worktree is an isolated working copy of a repository, so different tasks can be developed independently.

Use it to inspect workflow status, find ready tasks, detect dependencies and collisions, let the user choose what to launch, and start or resume the corresponding work.

It prevents work from starting when a contract is blocked, duplicated, cyclic, or already running. It also helps resume existing work instead of creating duplicate worktrees.

wf-run — Skill for Claude Code by tomsej/pi-ext

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 tomsej/pi-ext --skill wf-run

Clone the repo

git clone --depth 1 https://github.com/tomsej/pi-ext

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-run/github.svg)](https://agentmods.dev/skills/tomsej/pi-ext/wf-run)

Your own site

<a href="https://agentmods.dev/skills/tomsej/pi-ext/wf-run"><img src="https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-run/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/tomsej/pi-ext/wf-run"><img src="https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 85 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,323 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Agent Snooping · line 49
Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.

Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00085	$0.01323
Opus 5.5	$0.00034	$0.00529
Sonnet 5.5	$0.00017	$0.00265
Haiku 4.5	$0.00009	$0.00132

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

Security

Grade A, and why

wf-run 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.

skills/wf-run/SKILL.md · 83 lines

How it starts

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

/wf-run — naplánuj a spusť kontrakty

Jsi v HLAVNÍ session: plánuješ, spouštíš worktree, předáváš — nikdy tu nic neimplementuješ. Před sc worktree create si přečti sc instructions worktree.

GATE = node ~/Workspace/pi-ext/wf/wf-gate.mjs

1. Stav

GATE status --json (z rootu repa) odvodí stav živě z gitu a gh:

done → po schválení archivuj celý adresář kontraktu: mv <dirname(file)> <specs dir>/_archive/ (cesty z JSONu; specy jsou mimo repo, žádný git).
pr-open s nevyřešenými thready → kandidát na „vyřeš komentáře".
blocked → čeká na merged kontrakty z after; nespouštěj.
cycle → chybný cyklus v after; oprav kontrakty, nespouštěj.
launching → atomický claim drží jiný launcher; nikdy nespouštěj create.
running → právě jeden dirigující worktree; kandidát na resume.
duplicate → více .wf/active pro stejný spec; nespouštěj nic — eskaluj porovnání a ponechání jediného canonical worktree.

2. Plán

launch — ready
resume — session najdi přes sc agents list --output json (podle worktree/branch ze status JSONu); navrhni follow-up, ne nový worktree.
attention — pr-open s nevyřešenými thready

Kolize: přečti Scope každého spustitelného kontraktu. Dva specy na stejné soubory nesmí běžet paralelně — doporuč sekvenci a řekni proč.

Ukaž tabulku s jasným doporučením a ZEPTEJ se, co spustit (all / jména / recommended). Bez odpovědi nespouštěj nic.

3. Spuštění (pro každý vybraný spec)

Absolutní cesta ze GATE status --json (file) — ověř, že soubor existuje a stav je pořád ready.
GATE agents <spec> --json → conductor (null = pi s default modelem).
Připrav task soubor (tmp) přesně tohohle tvaru:

Načti ~/Workspace/pi-ext/skills/wf-impl/SKILL.md a proveď kontrakt na <absolutní cesta ke contract.md>. Kontrakt žije mimo repozitář — přečti ho z té přesné cesty. Pracuj jen v tomhle worktree. Nevytvářej worktree. Produktové rozhodnutí, které z kontraktu neodvodíš, napiš jako otázku do PR / review threadu a tu fázi pozastav.

Read the full file on GitHub · 83 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.

1mo ago First seen · 83 lines · 85 tokens per session scan A c98e6411c32f

Subscribe to this mod's changes

wf-run is a skill published in the GitHub repository tomsej/pi-ext (79 stars, last pushed 1mo ago), licensed MIT. It adds 85 tokens to every session and 1,323 once invoked, about $0.0003 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.

Git and workflow Planning

wf-run

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/wf-run — naplánuj a spusť kontrakty

1. Stav

2. Plán

3. Spuštění (pro každý vybraný spec)

What this file has done since we first saw it

Other skills, from other repositories

merge-batch

prowler-commit

gh-auth-isolation

comet-github

github-skill

release-helper