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 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/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.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.5 | $0.00014 | $0.00152 |
| Sonnet 5.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 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.
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.
- 1mo 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 (79 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 379 once invoked, about $0.0001 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.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…