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/ynishi/mlua-swarm/mse-wakenpx skills add ynishi/mlua-swarm --skill mse-wakegit clone --depth 1 https://github.com/ynishi/mlua-swarmWrote 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/ynishi/mlua-swarm/mse-wake)<a href="https://agentmods.dev/skills/ynishi/mlua-swarm/mse-wake"><img src="https://agentmods.dev/badge/skills/ynishi/mlua-swarm/mse-wake.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.1 | $0.00048 | $0.00549 |
| Opus 5 | $0.00024 | $0.00275 |
| Sonnet 5 | $0.00010 | $0.00110 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
mse-wake 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.
What it actually says
/mse-wake — Load mse Blueprint authoring context
Fetches the schema + guides + sample inventory once, at the start of a
Blueprint design conversation, so the main thread has the right vocabulary
before the User asks (or the AI decides) to invoke @mse-adviser or
/bp-build.
When to run
- Start of a session where the User wants to design or discuss a mlua-swarm Blueprint.
- Before the AI reasons about
flownodes, worker binding, projection placement, verdict contracts, or operator kinds — anything where the schema field names matter.
Runs load-only. If the User just wants an answer to one question, prefer
@mse-adviser directly (it does its own grounding fetches).
What it loads
- Blueprint JSON Schema —
mse://api/blueprint-schemaviaReadMcpResourceTool. - Guide inventory — list
mse://guides/*viaListMcpResourcesTooland read the two lifecycle entry points:mse://guides/getting-startedandmse://guides/bp-lifecycle. - Sample inventory — list
mse://blueprints/samples/*viaListMcpResourcesTool. Do not read every sample body; a single representative sample body (mse://blueprints/samples/07-dsl-pipeline) is enough to seed the DSL vocabulary. - MCP tool reference —
mse://guides/mcp-tool-referenceso thebp_build/bp_doctor/swarm_run/mse_operator_*shapes are accessible.
What it does not do
- Does not spawn an agent (
@mse-adviser/@bp-coder). - Does not write files.
- Does not register or run a Blueprint.
After it runs
The main thread continues normally. Typical next moves:
- Design consultation →
@mse-adviserwith a specific question. - Kick implementation once design is mature →
/bp-build "<design paragraph>". - Peek a specific sample →
ReadMcpResourceToolon the URI listed in the sample inventory.
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 · 53 lines · 48 tokens per session scan A f218a9e99125
mse-wake is a skill published in the GitHub repository ynishi/mlua-swarm (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 48 tokens to every session and 549 once invoked, about $0.0002 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-31.
Other skills, from other repositories
lint-js
Lint JS/TS code only. Use before opening a PR when only JavaScript or TypeScript files were changed (no Rust).
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
agent-pagerank-analyzer
Agent skill for pagerank-analyzer - invoke with $agent-pagerank-analyzer.
agent-neural-network
Agent skill for neural-network - invoke with $agent-neural-network.
worker-integration
Worker-Agent integration for intelligent task dispatch and performance tracking.