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-ospecgit 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-ospec)<a href="https://agentmods.dev/skills/waterplanai/agentic-config/ac-workflow-mux-ospec"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-workflow-mux-ospec/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-ospec"><img src="https://agentmods.dev/badge/skills/waterplanai/agentic-config/ac-workflow-mux-ospec.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.00032 | $0.01422 |
| Opus 5 | $0.00016 | $0.00711 |
| Sonnet 5 | $0.00006 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
ac-workflow-mux-ospec 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MUX Spec Orchestrator - pi adaptation (pimux runtime)
Use this skill to execute explicit spec stages through pimux while preserving mux-ospec semantics.
Binding activation
If the user explicitly invokes mux-ospec / ac-workflow-mux-ospec, 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-ospec requests in pi, the current session is a pimux-only cross-stage 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-ospecexecution. - 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 execute substantive stage work directly in the parent.
- Do not read, grep, or inspect repo files in the parent to figure out implementation details.
- The first real move is to spawn the authoritative stage-owning
pimuxchild. - The first observable parent tool call must be
pimux spawn. - If the parent does substantive inspection before spawn, stop, acknowledge protocol violation, discard parent-side conclusions, and restart from
pimux spawn.
Parent tool surface
While this skill is active, the parent is runtime-locked to pimux, AskUserQuestion, and say only:
- before first child:
pimux spawnonly AskUserQuestionis allowed only when the user has not provided an explicit spec path or inline prompt, or when a later required user gate is reached- 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
- 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 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 · 107 lines · 32 tokens per session scan A c2317d4b89e7
ac-workflow-mux-ospec is a skill published in the GitHub repository WaterplanAI/agentic-config (30 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 1,422 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
vfx-text-cursor
A video or hero-frame effect where a cursor reveals a sentence character by character with coloured trails, light streaks, and a final shimmer.
migrate-skills-between-libraries
Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
browse-and-evaluate
Use when exploring the ai-agent-skills catalog to find, compare, and evaluate skills before installing. Always use --fields to limit output size and --dry-run before committing to an install.
install-from-remote-library
Use when installing skills from a shared ai-agent-skills library repo. Inspect with --list first, prefer --collection, and preview with --dry-run before installing.