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 WaterplanAI/agentic-config --skill ac-workflow-mux-roadmapgit clone --depth 1 https://github.com/WaterplanAI/agentic-configWrote 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/waterplanai/agentic-config/ac-workflow-mux-roadmap)<a href="https://agentmods.dev/skills/waterplanai/agentic-config/ac-workflow-mux-roadmap"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-workflow-mux-roadmap/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/waterplanai/agentic-config/ac-workflow-mux-roadmap"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-workflow-mux-roadmap.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.00035 | $0.01336 |
| Opus 5 | $0.00017 | $0.00668 |
| Sonnet 5 | $0.00007 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
ac-workflow-mux-roadmap 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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MUX Roadmap Orchestrator - pi adaptation (pimux runtime)
Use this skill to execute roadmap phases with mux-family semantics while using pimux as the authoritative orchestration runtime.
Binding activation
If the user explicitly invokes mux-roadmap / ac-workflow-mux-roadmap, or embeds this skill text as the runtime for the task, treat this document as a binding runtime contract, not as optional guidance, commentary, or a planning reference.
Absolute compliance rule
For explicit mux-roadmap requests in pi, the current session is a pimux-only roadmap orchestrator.
- FIRST after spawn: do not poll pimux or use Bash sleep/wait loops; wait for delivered child bridge activity.
- The authoritative
pimuxextension applies a fail-closed parent control-plane lock for explicitmux-roadmapexecution. - Before the first child exists, the parent must not call
Read,Bash,Edit,Write,NotebookEdit,Grep,Glob,web_search,subagent, or any other non-pimuxtool for substantive repo work. - Do not inspect roadmap files, phase docs, or repo targets in the parent before spawn.
- Do not resolve DAG details, implementation plans, or edit scopes from the parent.
- Do not collapse the roadmap -> phase -> stage ownership model by doing phase work directly in the current session.
- The first real move is to spawn the authoritative phase-owning
pimuxchild. - The first observable parent tool call must be
pimux spawn. - If you have not spawned that child yet, you are not allowed to analyze the roadmap or answer phase execution questions from the parent.
- If the parent performs substantive repo inspection or any forbidden tool call before spawn, stop immediately, acknowledge a protocol violation, discard any parent-side conclusions, and restart from
pimux spawn.
Parent tool surface
While this skill is active, the parent session is runtime-locked to pimux, AskUserQuestion, and say only:
- before the first child exists:
pimux spawnonly AskUserQuestionis allowed only when the user has not provided an explicit roadmap/spec path or inline prompt that is sufficient to spawn- after spawn: notify-first, not poll-first; wait for delivered child bridge activity instead of inspecting live state
- do not poll pimux or use Bash sleep/wait loops; if you are about to inspect routine progress, stop and wait for delivered child activity instead
- child bridge notifications are delivered automatically; use notify-first pacing
- happy path after spawn forbids
status,capture,tree,list, andopen; those are recovery-only tools for explicit live inspection, suspected stall/protocol violation/failure, or the inactivity watchdog - after a child progress report arrives, use at most one
send_messagewhen the child needs input; then wait for closeout or another child report - terminal settlement re-arms exactly one final
pimux statusverification before advancing sayis allowed only for short user-attention prompts
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.
- 10d ago First seen · 102 lines · 35 tokens per session scan A 88b5c753650f
ac-workflow-mux-roadmap is a skill published in the GitHub repository WaterplanAI/agentic-config (30 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,336 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-30.
Other skills, from other repositories
retro
CP-7 retrospective: audit checkpoints, evidence quality, action items, and harvest candidates. Closes the V-model cycle and feeds the next run. Use via /retro after ship, escalate, or significant session.
create-user-story
Create user stories with duplicate checking across any project tracker (Linear, GitHub Issues, Jira).
meeting-transcript
Process meeting recordings and notes into structured decisions, action items, and team dynamics with intelligent noise filtering.
team-brief
Generate daily team intelligence brief by cross-referencing GitHub, Linear, Slack, PostHog, meetings, and braindumps with two-way Linear sync-back.
update-knowledge-base
Maintain and update product knowledge base from releases, features, and project changes with optional wiki sync.
sync
Promote a change's delta specs into the canonical specs, without archiving. Use when the user wants to update the source-of-truth specs from a change: "sync the specs", "update the canonical specs", "promote the specs". Part of speclaw's lawbook module (draft → build → sync → archive).