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 multiplex-ai/muggle-ai-teams --skill blueprintgit clone --depth 1 https://github.com/multiplex-ai/muggle-ai-teamsWrote 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/multiplex-ai/muggle-ai-teams/blueprint)<a href="https://agentmods.dev/skills/multiplex-ai/muggle-ai-teams/blueprint"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-teams/blueprint/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/multiplex-ai/muggle-ai-teams/blueprint"><img src="https://agentmods.dev/badge/skills/multiplex-ai/muggle-ai-teams/blueprint.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.00122 | $0.01168 |
| Opus 5.5 | $0.00049 | $0.00467 |
| Sonnet 5.5 | $0.00024 | $0.00234 |
| Haiku 4.5 | $0.00012 | $0.00117 |
Grade A, and why
blueprint 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 2d 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.
This is a copy
100% identical to blueprint — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Blueprint — Construction Plan Generator
Turn a one-line objective into a step-by-step construction plan that any coding agent can execute cold.
When to Use
- Breaking a large feature into multiple PRs with clear dependency order
- Planning a refactor or migration that spans multiple sessions
- Coordinating parallel workstreams across sub-agents
- Any task where context loss between sessions would cause rework
Do not use for tasks completable in a single PR, fewer than 3 tool calls, or when the user says "just do it."
How It Works
Blueprint runs a 5-phase pipeline:
- Research — Pre-flight checks (git, gh auth, remote, default branch), then reads project structure, existing plans, and memory files to gather context.
- Design — Breaks the objective into one-PR-sized steps (3–12 typical). Assigns dependency edges, parallel/serial ordering, model tier (strongest vs default), and rollback strategy per step.
- Draft — Writes a self-contained Markdown plan file to
plans/. Every step includes a context brief, task list, verification commands, and exit criteria — so a fresh agent can execute any step without reading prior steps. - Review — Delegates adversarial review to a strongest-model sub-agent (e.g., Opus) against a checklist and anti-pattern catalog. Fixes all critical findings before finalizing.
- Register — Saves the plan, updates memory index, and presents the step count and parallelism summary to the user.
Blueprint detects git/gh availability automatically. With git + GitHub CLI, it generates full branch/PR/CI workflow plans. Without them, it switches to direct mode (edit-in-place, no branches).
Examples
Basic usage
/blueprint myapp "migrate database to PostgreSQL"
Produces plans/myapp-migrate-database-to-postgresql.md with steps like:
- Step 1: Add PostgreSQL driver and connection config
- Step 2: Create migration scripts for each table
- Step 3: Update repository layer to use new driver
- Step 4: Add integration tests against PostgreSQL
- Step 5: Remove old database code and config
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.
- 2d ago First seen · 106 lines · 122 tokens per session scan A f74f4f312e2c
blueprint is a skill published in the GitHub repository multiplex-ai/muggle-ai-teams (2 stars, last pushed 2d ago), licensed MIT. It adds 122 tokens to every session and 1,168 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to blueprint, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
codex-handoff
Three-phase delivery workflow — Claude plans and writes a spec, a Claude subagent implements in the host working tree, a fresh Codex session adversarially reviews the diff (via the codex-plugin-cc plugin). Implementation and review are never the same model. Use for any change touching more than one file or real…
discuss
Decision-lock workflow for complex features. Asks targeted domain-specific questions, locks scope, and writes a CONTEXT.md that downstream skills consume. Auto-invoked when a feature touches 3+ files across 2+ concerns, or manually via /discuss.
skill-name
One-line description of what this skill does and when it triggers.
codex-handoff
Three-phase delivery workflow — Claude plans and writes a spec, a Claude subagent implements in the host working tree, a fresh Codex session adversarially reviews the diff (via the codex-plugin-cc plugin). Implementation and review are never the same model. Use for any change touching more than one file or real…
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.