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 agentmods add skills/rse/ase/ase-meta-workflownpx skills add rse/ase --skill ase-meta-workflowgit clone --depth 1 https://github.com/rse/aseWrote 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/rse/ase/ase-meta-workflow)<a href="https://agentmods.dev/skills/rse/ase/ase-meta-workflow"><img src="https://agentmods.dev/badge/skills/rse/ase/ase-meta-workflow.svg" alt="Measured on agentmods" 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 | $0.00077 | $0.03953 |
| Opus 5 | $0.00039 | $0.01976 |
| Sonnet 5 | $0.00015 | $0.00791 |
| Haiku 4.5 | $0.00008 | $0.00395 |
Grade A, and why
ase-meta-workflow 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 5d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@${CLAUDE_SKILL_DIR}/../../meta/ase-control.md @${CLAUDE_SKILL_DIR}/../../meta/ase-skill.md @${CLAUDE_SKILL_DIR}/../../meta/ase-getopt.md
$ARGUMENTS
References
-
The following is a reference skill demonstrating the usual layout of a generated workflow skill -- its frontmatter, its
ase metapreamble, and the indentation of its<flow>:IMPORTANT: is authoritative for the usual layout only. The syntax of every control construct is defined exclusively by the
Control Flow Constructssection above, and its frontmatter and preamble show theclaudeflavor only -- the actual frontmatter fields and the actual preamble are dispatched on as defined by theGenerated Skill Contractbelow. -
The following is the ASE workflow graph, carrying one
<from/> -> <to/>transition per line, where each side is either anase-xxx-xxxskill or an upper-case logical state (START,SKETCH,APPROACHES,TASK,ARTIFACT,END):The tells which ASE skill sequences are usually meaningful. It guides the workflow, but it does not restrict it: a workflow may contain arbitrary non-ASE actions, and it may contain ASE transitions the does not list.
-
The following is the accumulated help of all ASE skills -- the concatenation of every skill's
help.mdfile -- and is the sole source for the options and arguments of every<skill/>invocation (for anase-xxx-xxxskill) you emit:
Generated Skill Contract
A generated skill is a regular skill of the current agent tool which is independent of the ASE plugin installation path. It therefore MUST strictly follow this contract:
-
Frontmatter:
name: <new-skill-name/>and adescriptionof one to three sentences summarizing the workflow and its trigger phrases.The remaining frontmatter fields are tool-specific, because every agent tool accepts its own field set and its own
allowed-toolsgrammar, and hence have to be dispatched on :
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.
- 5d ago First seen · 379 lines · 77 tokens per session scan A 67df6fe858ca
ase-meta-workflow is a skill published in the GitHub repository rse/ase (47 stars, last pushed 8d ago), licensed Apache-2.0. It adds 77 tokens to every session and 3,953 once invoked, about $0.0004 per session on Opus 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
hns-lsel-curator
Local Self-Evolution Loop (LSEL) curator — the CLUSTER + drain engine for the GOOS-local PROPOSE→APPLY seam closure (SPEC-LSEL-LOCAL-EVOLUTION-001). Companion-offset drain of .moai/lessons-inbox.jsonl with a drain-side severity filter that drops the 65% Bash-timeout/sandbox noise, eventkey clustering with a frequency…
moai-workflow-worktree
Git worktree management for parallel SPEC development with isolated workspaces, automatic branch registration, and seamless MoAI-ADK integration. Use when setting up parallel development environments.
hns-workflow-ci-loop
Unified CI watch + auto-fix loop skill. Polls gh pr checks after /moai sync PR creation, classifies required vs auxiliary failures, attempts safe automated patches (max 3 iterations), and escalates semantic failures to the user. Use for CI loop workflow — NOT for general loop iteration patterns (see…
moai-harness-learner
Harness learning subsystem coordinator. Produces Tier 4 auto-update proposal payloads consumed by the orchestrator (which surfaces them via AskUserQuestion) and orchestrates Apply/Rollback flows. Triggers when harness learning proposals are pending or learning lifecycle management is needed.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…
hns-oss-docs-readme-sync
README 4-file synchronization procedure for the oss-docs harness: Korean README.ko.md as primary source, en/ja/zh derivation, the shared language-switcher header contract, section-order parity checklist, and the manual verification recipe (no linter exists for READMEs). Loaded by the content-author and…