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-statusnpx skills add tomsej/pi-ext --skill wf-statusgit 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-status)<a href="https://agentmods.dev/skills/tomsej/pi-ext/wf-status"><img src="https://agentmods.dev/badge/skills/tomsej/pi-ext/wf-status.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.00035 | $0.00379 |
| Opus 5 | $0.00017 | $0.00189 |
| Sonnet 5 | $0.00007 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
wf-status 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 6d 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.
What it actually says
/wf-status — contract overview
GATE = node ~/Workspace/pi-ext/wf/wf-gate.mjs
- Run
GATE status --jsonfrom the repo root (human table: without --json). States are derived live: ready / blocked (after) / cycle / launching (claim before worktree begin) / running / duplicate / pr-open / done. - Present the table in Czech and add recommended actions:
done→ offer to archive:mv <adresář kontraktu> <specs dir>/_archive/(each contract is a directory~/Workspace/specs/<project>/<name>/holding contract.md and its artifacts, outside any repo — no commits or PRs involved; derive the directory from thefilepath in the status JSON).pr-openwith unresolved threads → offer dispatching the worktree session via wf-run's resolve-comments action.blocked→ name unmet prerequisites;cycle→ require contract repair.launching→ never retry create; wait for claim transition or expiry.duplicate→ list every worktree and require reconciliation to one canonical.runningwith an old last commit → flag as possibly stalled; offer resume via wf-run. A running implementation can be inspected via/subagents.readyspecs → mention wf-run to launch them.
- Take no action without the user's approval. This skill reads; it mutates only the approved archive commits.
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.
- 6d ago First seen · 29 lines · 35 tokens per session scan A bf86e27b095a
wf-status is a skill published in the GitHub repository tomsej/pi-ext (69 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 379 once invoked, about $0.0002 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…
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…
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…
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…