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/tomsej/pi-ext/wf-runnpx skills add tomsej/pi-ext --skill wf-rungit clone --depth 1 https://github.com/tomsej/pi-extWrote 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/tomsej/pi-ext/wf-run)<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="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.1 | $0.00085 | $0.01323 |
| Opus 5 | $0.00043 | $0.00661 |
| Sonnet 5 | $0.00017 | $0.00265 |
| Haiku 4.5 | $0.00009 | $0.00132 |
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 5d 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 — 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-opens nevyřešenými thready → kandidát na „vyřeš komentáře".blocked→ čeká na merged kontrakty zafter; nespouštěj.cycle→ chybný cyklus vafter; 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/activepro 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(podleworktree/branchze status JSONu); navrhni follow-up, ne nový worktree. - attention —
pr-opens 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řádready. -
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.mda 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.
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.
- 5d ago First seen · 83 lines · 85 tokens per session scan A c98e6411c32f
wf-run is a skill published in the GitHub repository tomsej/pi-ext (69 stars, last pushed 2d ago), licensed MIT. It adds 85 tokens to every session and 1,323 once invoked, about $0.0004 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…