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-rungit 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-run)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-workflow-run"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-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.
<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-workflow-run"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-run.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.00082 | $0.04261 |
| Opus 5.5 | $0.00033 | $0.01704 |
| Sonnet 5.5 | $0.00016 | $0.00852 |
| Haiku 4.5 | $0.00008 | $0.00426 |
Grade A, and why
wise-workflow-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 23d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wise-workflow-run - the conductor
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.
The wise_* tools (wise_status, wise_preflight, wise_run,
wise_wait, wise_answer, wise_cancel, wise_nudge, wise_resume)
come from the managed wise-engine MCP server; Claude Code shows them
with a server prefix. Errors return {"error":{code,message,...}}.
Arguments
$ARGUMENTS: first token is the workflow name (empty: run
"$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" list-defs, pick with
AskUserQuestion plus Abort). Remaining tokens fill the declared inputs
in order; the last declared input absorbs the rest of the line.
1. Init check
Call wise_status (no id). Workflows do not read the session profile
set by /wise-profile; pre-flight asks harness, provider permissions, model and effort
instead.
wise_*tools missing: follow host-control diagnostics. Use the registered CLI route when available; repair missing or stale registration through init.DAEMON_UNAVAILABLE: inspect the daemon error through the CLI. Fix the reported startup/dependency/socket problem before retrying; reloading the host alone does not repair it.AUTH_REQUIRED: printlogin_cmdverbatim and stop.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 23d ago Changed · +23 lines 16d484a32207
- 1mo ago Changed · +15 lines ace883bdf218
- 1mo ago Changed · +51 lines 5afc2082ca11
- 1mo ago Changed · +27 lines 0af2e9419b37
- 1mo ago Changed · +9 lines 17e1053289f4
- 1mo ago Changed · +14 lines c35c2ee92865
- 1mo ago Changed · +26 lines d5241b7fb173
- 1mo ago Changed · -652 lines · -47 tokens per session 009bf5afd539
- 1mo ago First seen · 793 lines · 129 tokens per session scan A 5d5bbfe0ec25
wise-workflow-run is a skill published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 82 tokens to every session and 4,261 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-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.