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 ultragoalgit 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/ultragoal)<a href="https://agentmods.dev/skills/mrzhangguoguo/oh-my-workbuddy/ultragoal"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/ultragoal/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/ultragoal"><img src="https://agentmods.dev/badge/skills/mrzhangguoguo/oh-my-workbuddy/ultragoal.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.01830 |
| Opus 5 | $0.00017 | $0.00915 |
| Sonnet 5 | $0.00007 | $0.00366 |
| Haiku 4.5 | $0.00003 | $0.00183 |
Grade A, and why
ultragoal 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 12d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ported from oh-my-codex
ultragoal. OMX runtime conventions ($macroinvocation,omxCLI,.omx/state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list,.workbuddy/memory).
Ultragoal Workflow
Use when the user asks for durable multi-goal planning or sequential execution over a set of stories/objectives. Ultragoal turns a brief into repo-native artifacts and drives them to verified completion. There is no Codex /goal mode or omx ultragoal CLI — tracking is the task list (the live goal board), memory (durable brief/ledger), and optional files under .omw/ultragoal/.
Durable artifacts
.omw/ultragoal/brief.md— the original brief and constraints..omw/ultragoal/ledger.jsonl— checkpoint and structured steering audit events (append-only).- The task list is the live source of truth for goal/story state.
Write the brief once at creation via the Write tool. Append every checkpoint/steering decision to ledger.jsonl.
Create goals
- Capture the brief (from argument, a pasted file, or a
brief.mdpath) into.omw/ultragoal/brief.md. - Decompose into goals/stories. For each, create a task with
TaskCreate:subject: short goal titledescription: objective, acceptance criteria, constraintsowner:leader(Ultragoal stays leader-owned)addBlockedBy/addBlocksfor dependencies
- Set the first story
in_progress; keep the restpending. - Inspect the board and refine if needed (reorder, split, reword).
Complete goals
Loop until the task list reports all goals complete:
- Run
ultragoal complete-goals(i.e. pick the nextin_progressstory). - Read the printed handoff (the story description).
- If the story benefits from parallel execution, invoke the
teamskill (skill: team) and pass Team the evidence; the leader stays Ultragoal owner. - Complete ONLY the current story. Use a lighter model for planning if available; use the appropriate execution skills (
plan,skill: tdddiscipline, etc.). - Run a completion audit against the story objective and real artifacts/tests.
- In aggregate mode, do not mark sibling stories done from one story; checkpoint only the finished story. On the final story only, first run the mandatory final cleanup/review gate below, then mark complete.
- Checkpoint the durable ledger with evidence: append to
.omw/ultragoal/ledger.jsonl:{"goal_id":"<id>","status":"complete","evidence":"<tests/files/review evidence>","at":"<now>"} - If blocked/failed, checkpoint failure:
{"goal_id":"<id>","status":"failed","evidence":"<blocker/evidence>","at":"<now>"} - Resume failed goals by re-opening the task (
TaskUpdate→in_progress) and re-running.
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.
- 12d ago First seen · 117 lines · 35 tokens per session scan A cd3d9623b666
ultragoal is a skill published in the GitHub repository mrzhangguoguo/oh-my-workbuddy (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,830 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-31.
Other skills, from other repositories
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-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).
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…
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.
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…