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-resumegit 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-resume)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-workflow-resume"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-resume/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-resume"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-resume.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.00100 | $0.01034 |
| Opus 5.5 | $0.00040 | $0.00414 |
| Sonnet 5.5 | $0.00020 | $0.00207 |
| Haiku 4.5 | $0.00010 | $0.00103 |
Grade A, and why
wise-workflow-resume 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wise-workflow-resume
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.
Tools come from the managed wise-engine MCP server. Errors return
{"error":{code,message,...}}. Diagnose DAEMON_UNAVAILABLE through host
control before retrying. For AUTH_REQUIRED, print the selected provider's
login_cmd verbatim and stop.
1. Pick the run
wise_status (no id) lists every run. Resumable: paused, failed.
gated runs are answered, not resumed. running runs are only
followed.
- Argument given:
wise_status {run_id}. OnRUN_NOT_FOUND, usepython3 "${WISE_PLUGIN_ROOT}/scripts/wise-helpers.py" runs-rootto locate history. Astate.yamlentry is a legacy v1 run: reportLegacy run cannot resume. Import its definition, review it, then start a new v2 run.Keep its files unchanged. Otherwise printNo run <run_id>.and stop. - No argument: use the host control reference's explicit-answer route over the
paused,failed,gatedruns (labelrun_id; description<workflow>, <status>, last activity <last_activity_at>, <cwd>) plus Abort. None: printNo resumable runs. /wise-workflow-status lists all runs.and stop.
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 · +6 lines 6a7f0c9660c4
- 1mo ago Changed · +21 lines 8b154d2bb6ff
- 1mo ago Changed · -238 lines · -23 tokens per session scan C → A bb5762cc6026
- 1mo ago First seen · 297 lines · 123 tokens per session scan C b15ed587515a
wise-workflow-resume is a skill published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 100 tokens to every session and 1,034 once invoked, about $0.0004 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.