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-listgit 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-list)<a href="https://agentmods.dev/skills/e1024kb/wise-claude/wise-workflow-list"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-list/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-list"><img src="https://agentmods.dev/badge/skills/e1024kb/wise-claude/wise-workflow-list.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.00099 | $0.00983 |
| Opus 5.5 | $0.00040 | $0.00393 |
| Sonnet 5.5 | $0.00020 | $0.00197 |
| Haiku 4.5 | $0.00010 | $0.00098 |
Grade A, and why
wise-workflow-list 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/wise-workflow-list — list available workflows
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.
Why this skill exists
Users need a quick way to see which workflows they can run. Workflows
come from two places: bundled defaults under ${WISE_PLUGIN_ROOT}/workflows/
(shipped with the plugin) and user-authored ones under
the user_root from engine/engine.sh definition-roots (written by
/wise-workflow-create). Under each root, a workflow can live in one of
two layouts — <name>/workflow.yaml (folder form, preferred) or
<name>.yaml (legacy flat form). This skill lists both layouts from
both roots and flags any name collisions (a user def shadows a bundled
def of the same name).
Arguments
This skill takes no arguments. Ignore anything the user types beyond the skill name.
Procedure
1. Init-check + list — in ONE message
Run the init-check per ${WISE_PLUGIN_ROOT}/references/init-check.md,
firing init-registry.py check and the data call
"$HOME/.local/share/wise/bin/wise-engine" --wise-host "$WISE_HOST" list-defs together in one message. On INIT:ok, use the
list-defs output and jump to §2; otherwise follow the reference's
fallback. This skill is read-only, so on BOOTSTRAP:need-python it
relays the OPTION: lines and stops rather than driving an install
loop.
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 · +5 lines 8a4f17f7704c
- 1mo ago Changed · +12 lines · -5 tokens per session 6a7879e57c94
- 1mo ago First seen · 92 lines · 104 tokens per session scan A 8b0bdb3fd2a7
wise-workflow-list is a skill published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 99 tokens to every session and 983 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.