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/bp-buildnpx skills add ynishi/mlua-swarm --skill bp-buildgit 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/bp-build)<a href="https://agentmods.dev/skills/ynishi/mlua-swarm/bp-build"><img src="https://agentmods.dev/badge/skills/ynishi/mlua-swarm/bp-build.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.00072 | $0.00802 |
| Opus 5 | $0.00036 | $0.00401 |
| Sonnet 5 | $0.00014 | $0.00160 |
| Haiku 4.5 | $0.00007 | $0.00080 |
Grade A, and why
bp-build 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/bp-build — Blueprint Implementation Kick
Hands a mature design_para and a resolved output_path to @bp-coder
and lets it write the Blueprint in an isolated context, using bp_doctor
as the verify gate.
Either the User invokes /bp-build "<design_para>" --out=<path> literally,
or the AI invokes it on the User's behalf once the design conversation has
matured (see "Maturity Self-check" below).
Run only when main-thread dialogue (User ↔ AI) has condensed the design into a single paragraph. Never trigger mid-conversation with a vague intent, unnamed flow shape, or missing pass conditions.
Maturity Self-check (AI-invoked path)
Before assembling the kick prompt on the User's behalf, verify all of the following from the conversation context. If any item is missing, do not invoke — return one short question to the User to fill the gap, then resume.
- Blueprint name / id is decided (kebab-case, no collision concern).
- Flow shape is stated (which node kinds compose the top-level flow —
step/seq/branch/loop/fanout/try/assign). - Worker binding is stated (each agent's kind:
Lua/Automate/MainAi/AgentBlock/ subprocess backend — or an explicit "reuse existing agent id" declaration). - Verdict / projection expectations are stated (what shape lands in
final_ctx; which per-step outputs are named parts vs. plain body). - Output path is decided (absolute path ending
.jsonor.bp.lua). - Smoke intent is decided (
smoke: true= run once after doctor clears with a minimalinit_ctx; defaultfalse).
If any of 1–6 is missing, ask one short question rather than guessing.
Kick prompt shape
Dispatched to @bp-coder with the following literal template:
Blueprint output path: <absolute path, .json or .bp.lua>
Format: <json|lua> # derived from the path suffix
Smoke: <true|false> # default false
Design paragraph:
<design_para verbatim>
Optional grounding refs (Read before writing):
- <mse://guides/... URIs the design references, when applicable>
- <mse://blueprints/samples/... URIs the design references, when applicable>
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 · 73 lines · 72 tokens per session scan A b62c2af0dbf1
bp-build is a skill published in the GitHub repository ynishi/mlua-swarm (1 stars, last pushed today), licensed Apache-2.0. It adds 72 tokens to every session and 802 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-31.
Other skills, from other repositories
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-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.
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.