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 performance-goalgit 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/performance-goal)<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/performance-goal"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/performance-goal/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/performance-goal"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/performance-goal.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.00075 | $0.00805 |
| Opus 5 | $0.00037 | $0.00402 |
| Sonnet 5 | $0.00015 | $0.00161 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
performance-goal 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 11d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ported from oh-my-codex
performance-goal. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Performance Goal Workflow
Use this skill when the user asks to optimize performance and wants a goal-oriented loop with a measurable pass/fail contract, not a one-off review.
Contract
- WorkBuddy owns durable workflow state under
.omw/performance-goal/<slug>.md. - No optimization work may start until an evaluator command and a pass/fail contract exist.
- Do not declare the goal complete until the evaluator has a passing checkpoint and a completion audit proves the objective is met.
- Shell commands never mutate hidden runtime goal state — they run the evaluator and write evidence artifacts.
Setup (no omx CLI)
- Create a context snapshot in
.omw/performance-goal/<slug>.mdcontaining:objective: the measurable target (e.g. "reduce CLI startup p95 latency by 20%").evaluator_command: the command that produces the benchmark (e.g.npm run perf:startup).evaluator_contract: the PASS definition (e.g. "p95 latency improves >=20% AND regression tests pass").status:created.
- Record the same in the task list via
TaskCreate(one task per phase: start, optimize, checkpoint, complete).
If no workflow exists yet, do step 1 before any optimization.
Agent Loop
- Read the snapshot at
.omw/performance-goal/<slug>.md; if absent, run the Setup step. - Follow the handoff:
- Work only against the declared evaluator contract.
- Optimize in small, reversible patches.
- Run the evaluator and related regression tests.
- Record each result as a checkpoint in the snapshot (
pass/fail/blocked) with evidence text.
- Optimize in small reversible patches; run the evaluator and regression tests after each.
- Record every checkpoint (
pass/fail/blocked) in the snapshot with evidence. - Complete only when a
passcheckpoint exists and no required work remains.
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.
- 11d ago First seen · 58 lines · 75 tokens per session scan A edd5981ce433
performance-goal is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 75 tokens to every session and 805 once invoked, about $0.0004 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
performance-optimization
Optimizes application performance across frontend, backend, queries, and databases. Use when performance requirements exist, when you suspect performance regressions, when Core Web Vitals or load times need improvement, when N+1 query patterns need fixing, or when profiling reveals bottlenecks.
gke-node-notready
Diagnoses GKE nodes reporting NotReady or Unknown status by inspecting node conditions, events, kubelet/containerd logs, and node metrics, then proposing safe remediations. Use when nodes show NotReady, when the kubelet stops posting node status, or when workloads are evicted or stuck Pending due to node health. Don't…
gke-ai-troubleshooting-tpu-vbar-oom
Diagnoses and prevents vbarcontrolagent segfaults, out-of-memory (OOM) errors, and TPU device initialization failures on TPU v6e nodes in GKE caused by race conditions during TPU device resets or high-frequency metrics polling. Use when troubleshooting vbarcontrolagent crashes, memory cgroup OOMs in serial console…
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
comet-hotfix
A quick workflow for fixing an existing bug in Comet, a tool that manages structured code changes. It moves through opening the change, building, checking, and archiving it.
comet-hotfix
Comet preset path: Bug fix / hotfix. Skip brainstorming, directly open → build → verify → archive. Applicable for behavior fixes, scenarios not involving new capability design.