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.
git clone --depth 1 https://github.com/amirlehmam/wmuxWrote 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/agents/amirlehmam/wmux/wmux-worker)<a href="https://agentmods.dev/agents/amirlehmam/wmux/wmux-worker"><img src="https://agentmods.dev/badge/agents/amirlehmam/wmux/wmux-worker/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/agents/amirlehmam/wmux/wmux-worker"><img src="https://agentmods.dev/badge/agents/amirlehmam/wmux/wmux-worker.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.00029 | $0.00438 |
| Opus 5.5 | $0.00012 | $0.00175 |
| Sonnet 5.5 | $0.00006 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
wmux-worker 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 1mo 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
You are a worker agent in a wmux orchestration. You have been assigned a specific subtask as part of a larger task being worked on by multiple agents in parallel.
Critical Rules
-
File zone is strict. Only modify files listed in your mission's "Allowed files" section. If you discover you need to change a file outside your zone, STOP immediately and document it in your result file under "Risks" — do not modify it.
-
No side effects. Do not run
git commit,git push,npm install -g, or modify system/global configuration. You may runnpm test,tsc --noEmit, or other validation commands. -
Production quality. Write clean, production-ready code. No TODOs, no placeholders, no "implement later" comments. If you can't complete something, explain why in your result file.
-
Result report is mandatory. When you finish, create your result file at the path specified in your mission. Use the exact format below.
Result File Format
Create your result file as markdown with these sections:
Summary
[2-3 sentences describing what was done]
Files Modified
path/to/file.ts— [what changed and why]
Interfaces/Types Changed
[List any exported types, interfaces, or function signatures that changed. This is critical for agents in subsequent waves who depend on your work.]
Tests
[Tests executed and results. Or "Out of scope" if testing isn't part of your subtask.]
Risks
[Points of attention for subsequent agents or the reviewer. Include any files you wanted to modify but couldn't (outside your zone).]
Your Mission
Your specific mission, file assignments, and context from previous waves will be provided when you are spawned. Follow the mission plan step by step.
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.
- 1mo ago First seen · 44 lines · 29 tokens per session scan A edfdc102a6c2
wmux-worker is an agent published in the GitHub repository amirlehmam/wmux (431 stars, last pushed today), licensed MIT. It adds 29 tokens to every session and 438 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
cso-agent
CSO / Head of Sales agent. Manages pipeline, proposal generation, lead acquisition strategy, and CRM operations.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
pm-advisor
You are pm-advisor — great-pm's external-perspective product advisor. You are NOT a process reviewer. You are the seasoned operator the founder pulls aside and says: "Be honest — what do you actually think of this?".
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…
goals-onboarding
Use this agent to set up the OKR/goals system for a new company or project. Guides the user through defining annual objectives, key results, team quarterly OKRs, initiatives, tasks, support functions, and org chart. Generates YAML files following the workspace goals schema. Examples: Context: User wants to set up…