ultrawork
Binding ultrawork mode directive for omo-senpi. When a prompt contains ultrawork or ulw, the omo input hook injects the full directive as a hidden custom message (customType omo-ultrawork:directive, display false) ahead of the user's text, which is left untouched; a prompt queued while the agent is streaming instead carries the directive appended inside that same message. The directive is present in the conversation context; on the idle path it is not shown in the visible prompt, while a queued prompt carries the directive visibly (exactly as before this change). When the directive is already
Profile →npx skills add code-yeongyu/oh-my-openagent --skill ultrawork --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
The skill binds ultrawork mode by monitoring prompts for ultrawork or ulw and injecting a hidden directive ahead of the user text via the omo input hook. When a prompt is streamed, the directive is carried inside the same message. The directive may be present in conversation context and is only read from this file when ultrawork is requested and the directive is not already present.
How it works
- It defines an ultrawork-mode directive and a mandatory initial user-visible line:
ULTRAWORK MODE ENABLED!. - It instructs the agent to read this file only if ultrawork mode is requested and the directive is not already in the conversation; otherwise, it should not re-read.
- It describes how the directive should be injected: as a hidden custom message with customType omo-ultrawork:directive and display false, ahead of the user's text. If a prompt is queued while streaming, the directive is appended inside the same hidden message.
- The directive remains in the conversation context on idle path, but not shown in the visible prompt; a queued prompt carries the directive visibly as before this change.
When to use it
Use when the user explicitly requests ultrawork mode (prompt contains ultrawork or ulw) and the directive is not already present in the conversation.
What it can touch
The skill mentions tools: claude-code, codex, cursor. It relies on the omo-senpi integration to inject the directive ahead of user text.
Caveats
License is NOASSERTION. The file indicates to treat the directive as a special hidden message and to avoid re-reading if already present in the conversation. It also states that the file should be read only when ultrawork mode is requested and the directive is not present.
<ultrawork-mode> **MANDATORY**: First user-visible line this turn MUST be exactly: `ULTRAWORK MODE ENABLED!` [CODE RED] Maximum precision. Outcome-first. Evidence-driven. # Role Expert coding agent. Ship verified work. No process narration. # Goal Deliver EXACTLY what the user asked, end-to-end working, proven by captured evidence: a failing-first proof that went RED→GREEN through the cheapest faithful channel, plus real-surface proof sized by the tier below. TESTS ALONE NEVER PROVE DONE — a green suite means the unit-level contract holds, not that the user-facing behavior works. # Tier triage (classify ONCE at bootstrap; record tier + one-line justification in the notepad; ratchet up only) Your change set is what THIS session will itself edit or execute; work handed to another session, thread, or delegated loop is payload and sizes THAT session's process, not yours. Launching it — sync, prompt, create, verify — is control-plane work: LIGHT however large the delegated project is. Default is LIGHT. Take HEAVY only when the change set hits a fact you can point to: a new module / layer / domain model / abstraction; auth, security, session-handling code, or permissions; building or cha
- 0. Survey the skills, gather context, then size the work
- 1. Create the goal with binding success criteria
- 2. Open the durable notepad
- 3. Write the plan to a file, then register obsessive todos via todo
What does the ultrawork skill do?
Binding ultrawork mode directive for omo-senpi. When a prompt contains ultrawork or ulw, the omo input hook injects the full directive as a hidden custom message (customType omo-ultrawork:directive, display false) ahead of the user's text, which is left untouched; a prompt queued while the agent is streaming instead carries the directive appended inside that same message. The directive is present in the conversation context; on the idle path it is not shown in the visible prompt, while a queued prompt carries the directive visibly (exactly as before this change). When the directive is already
How do I install it?
Run `npx skills add code-yeongyu/oh-my-openagent --skill ultrawork --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From code-yeongyu/oh-my-openagent, a repository with 67,209 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.