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 e1024kb/wise-claude --skill wise-workflow-statusgit clone --depth 1 https://github.com/e1024kb/wise-claudeWrote 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/e1024kb/wise-claude/wise-workflow-status)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-workflow-status"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-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/e1024kb/wise-claude/wise-workflow-status"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-status.svg" alt="Reviewed on agentmods" width="80" 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.00125 | $0.00762 |
| Opus 5.5 | $0.00050 | $0.00305 |
| Sonnet 5.5 | $0.00025 | $0.00152 |
| Haiku 4.5 | $0.00013 | $0.00076 |
Grade A, and why
wise-workflow-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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wise-workflow-status
Preferred model: opus; preferred effort: low. Resolve availability before work;
do not silently substitute.
Before executing, follow model fallback for unavailable models or delegation routes, including in autonomous procedures.
At every skill start, identify your main/child role and the current client and GUI/TUI question tools, then read and follow the question lifecycle. Keep asynchronous prompts open until answered; this rule does not authorize questions in autonomous or otherwise prompt-free procedures.
First read host control. Resolve the
loaded installation, set WISE_HOST to this conductor and WISE_PLUGIN_ROOT
to that installation. Use its managed launcher for shell commands. Follow the
reference's diagnostics and explicit-answer fallback when MCP or a native picker
is unavailable. Conductor host and child provider are independent.
wise_status comes from the managed wise-engine MCP server. On
DAEMON_UNAVAILABLE, follow host-control diagnostics before retrying.
No argument
wise_status {} returns RunSummary[], newest activity first. Render
one table: run id | workflow | status | started | cwd | children. The
children column lists each live child as <step> turn <n> <tool>, or
-. Empty list: No engine runs yet. If legacy history is requested,
get the canonical root with
python3 "${WISE_PLUGIN_ROOT}/scripts/wise-helpers.py" runs-root,
then use that helper's list-runs <root> command. It reports v1
entries as read-only legacy notices; they cannot resume. Keep all
history files unchanged.
With a run id
wise_status {run_id} returns one RunSummary. Print run id,
workflow, status, started, last activity, completed (when set), cwd,
children as above. RUN_NOT_FOUND: No run <run_id>.
Status gated: print gate.step and gate.message, then
AskUserQuestion Answer this gate now? with the gate's options plus
Not now (free text when allow_text); beyond the host's option cap
follow the
long option list rule
so every gate option stays reachable. On a choice, wise_answer {run_id, gate_id, value}, print gate answered, point to
/wise-workflow-resume <run_id> to follow the run.
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 Changed · +8 lines 8ad2a1e8a66f
- 1mo ago Changed · +14 lines 76feddc0bed7
- 1mo ago Changed · -36 lines · -16 tokens per session 1d89f5e68cbc
- 1mo ago First seen · 85 lines · 141 tokens per session scan A 3a472488e6bb
wise-workflow-status is a skill published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 125 tokens to every session and 762 once invoked, about $0.0005 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-09-05.
Other skills, from other repositories
stale-proposals
Audit this repository's local proposal queue for stale entries: proposals still marked proposed, deferred, or accepted even though the work already shipped, plus old proposals whose subject has become inert. Reconcile proposals against plugin changelogs and first-parent Git history, automatically resolve only…
pave-catalog
Build a service catalog — schema, starter entries, and governance model. Produces what information to capture per service, how it's maintained, and where it lives. Use when asked to "service catalog", "what services do we have", "catalog our services", "service inventory", or "who owns what".
atlas-present
Generate a polished HTML presentation page and Obsidian Canvas for big releases — new products, takeovers, major migrations. Non-technical audience. Use when asked to "present this", "release announcement", "show what we built", or "stakeholder update".
crest-narrative
Strategic narrative — write a standalone strategy memo that frames product direction, bets, and rationale for a planning horizon. Use when asked to "write a strategy doc", "product vision", "strategic narrative", "company strategy memo", "planning memo", or "explain our product direction".
crest-okr
OKR design — create objectives and key results with a North Star metric, input metrics tree, and cadence. Use when asked to "set OKRs", "define our objectives", "what should we measure this quarter", "design our OKR framework", "build a metrics tree", or "what's our North Star".
hermit-scribe
File a GitHub issue or post a comment on an existing issue via a GitHub App bot identity. Use when the operator says "file as a GH issue", "open an issue for PROP-NNN", "report this to the tracker", "add a comment to issue.