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 mrzhangguoguo/oh-my-workbuddy --skill workergit clone --depth 1 https://github.com/mrzhangguoguo/oh-my-workbuddyWrote 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/mrzhangguoguo/oh-my-workbuddy/worker)<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/worker"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/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/skills/mrzhangguoguo/oh-my-workbuddy/worker"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/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.00056 | $0.01311 |
| Opus 5 | $0.00028 | $0.00656 |
| Sonnet 5 | $0.00011 | $0.00262 |
| Haiku 4.5 | $0.00006 | $0.00131 |
Grade A, and why
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 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ported from oh-my-codex
worker. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Worker Protocol (WorkBuddy subagent)
This skill describes the discipline a WorkBuddy subagent (spawned via the Agent tool) should
follow when a leader assigns it a unit of work. In OMX this was a tmux-pane Team worker driven by
omx team api; in WorkBuddy there is no tmux runtime or omx binary. Coordination happens
through (a) the Agent's returned result, and (b) optional shared artifacts under
.omw/team/<team>/. The value preserved here is the claim-safe lifecycle, ACK-readback, and
evidence discipline — not the transport.
Identity
A worker is created by a leader who spawns an Agent with a clear identity and task. The identity looks like:
<team-name>/worker-<n> — e.g. alpha/worker-2.
Pass the identity and the full task into the Agent prompt. There is no OMX_TEAM_WORKER env
var to read; the prompt is the source of truth.
Startup Protocol (ACK)
- Parse the assigned identity into
teamName(before/) andworkerName(after/). - Send a startup ACK before task work: in your first response (or as the first line of your
returned result), state one short deterministic line, e.g.
ACK: worker-2 initialized. - After ACK, proceed to the assigned task.
If the team uses a durable mailbox artifact, write the ACK to
.omw/team/<teamName>/mailbox/<workerName>.md; otherwise the ACK lives in your returned message.
Inbox + Tasks
- Read the task from the Agent prompt (the leader embeds the task directly — there is no separate inbox file to poll).
- If the team uses durable task files, read
.omw/team/<teamName>/tasks/task-<id>.json; otherwise work from the prompt. - Pick the first unblocked task assigned to you.
- Claim the task (do NOT start work without a claim): record
{"state":"in_progress","owner":"<workerName>"}via TaskUpdate on the shared task list, or write it to the task file /.omw/team/<teamName>/workers/<workerName>/status.md. - Do the work.
- Complete/fail via lifecycle transition: move the task to
completedorfailedwith a shortresult/errornote — TaskUpdate on the task list, or write to the task file. Do not leave lifecycle fields ambiguous. - Write your worker status back:
.omw/team/<teamName>/workers/<workerName>/status.mdwith{"state":"idle", ...}(or mark the corresponding task done in the task list).
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 · 115 lines · 56 tokens per session scan A 3a2db6687b14
worker is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 56 tokens to every session and 1,311 once invoked, about $0.0003 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
execution-algo-trading
Institutional execution algorithms: TWAP, VWAP, Implementation Shortfall, POV, Iceberg orders, slippage analysis, market impact, and TCA. USE FOR: execution, TWAP, VWAP, implementation shortfall, slippage, market impact, TCA, iceberg order, POV, algo execution, transaction cost.
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.