Borrowing it
Nothing to install: this file belongs to Chachamaru127/codex-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Chachamaru127/codex-harness/main/.codex/skills/work/SKILL.mdgit clone --depth 1 https://github.com/Chachamaru127/codex-harnessWrote 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/chachamaru127/codex-harness/work)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/work"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/work.svg" alt="Measured on agentmods" 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.00091 | $0.02361 |
| Opus 5 | $0.00046 | $0.01180 |
| Sonnet 5 | $0.00018 | $0.00472 |
| Haiku 4.5 | $0.00009 | $0.00236 |
Grade B, and why
work scanned grade B with 1 finding 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 6d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
cat > .claude/state/work-active.json <<EOF How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work Skill
Plans.md のタスクを実装する主力スキル。スコープに応じて戦略を自動選択。
Philosophy
「聞いて、判断して、実行する」
1タスクなら直接実装。複数なら並列。大量なら自動反復。 ユーザーはスコープだけ決めれば、あとは自動。
Quick Reference
/work # スコープを聞いてから実行
/work 3 # タスク3だけ即実行
/work all # 全タスクを即実行
/work 3-6 # タスク3〜6を即実行
/work --codex # Codex MCP で実装（スコープを聞く）
/work --codex all # Codex MCP で全タスク即実行
/work --parallel 5 # 並列5ワーカーで実行
/work --no-commit # 自動コミット抑制
/work --resume latest # 前回セッション再開
Options
| Option | Description | Default |
|---|---|---|
all |
全未完了タスクを対象 | - |
N or N-M |
タスク番号/範囲指定 | - |
--codex |
Codex MCP で実装委託 | false |
--parallel N |
並列ワーカー数 | auto |
--sequential |
並列禁止（直列実行） | - |
--no-commit |
自動コミット抑制 | false |
--max-iterations N |
反復上限（all 時） | 10 |
--resume <id|latest> |
セッション再開 | - |
--fork <id|current> |
セッションフォーク | - |
Scope Dialog (引数なし時)
引数なしで呼ぶと、対話でスコープを確認:
/work
どこまでやりますか?
1) 次のタスク (推奨): Plans.md の次の未完了タスク
2) 全部: 残りのタスクを全て完了
3) 指定: タスク番号や範囲を指定 (例: 3, 3-6)
> [Enter = 1]
引数ありなら即実行（対話スキップ）。
詳細: references/scope-dialog.md
Auto Strategy Selection
スコープに応じて、内部戦略を自動選択:
| スコープ | 戦略 | 元スキル相当 |
|---|---|---|
| 1タスク | 直接実装 | 旧 /work |
| 2-3タスク | サブエージェント並列 | 旧 /work --parallel |
4+タスク or all |
サブエージェント並列 + 自動反復 | 旧 /ultrawork |
実行開始時に戦略を表示:
🔧 戦略: 直接実装 (タスク1件)
🔧 戦略: 並列 3 ワーカー (タスク3件)
🔧 戦略: 並列 3 ワーカー + 自動反復 (タスク8件, 最大10回)
ユーザーは戦略を意識する必要なし。
Default Flow
/work [scope]
↓
Phase 0: スコープ確認 (引数なしなら対話)
↓
Phase 1: 戦略選択 (タスク数で自動判断)
↓
Phase 2: 実装
→ 1タスク: 直接実装
→ 複数: task-worker サブエージェント並列
→ 全部/4+: 並列 + 反復ループ (完了まで自動)
↓
Phase 3: Review Loop (harness-review)
→ APPROVE: proceed
→ REQUEST_CHANGES: fix → re-review
↓
Phase 4: Auto-commit (unless --no-commit)
↓
Tip 表示
Auto-Iteration (4+ tasks or all)
大量タスク時は自動反復ロジックが有効化:
What ships with it
10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- CLAUDE.md 689 B
- references/auto-commit.md 2.5 KB
- references/auto-iteration.md 7.7 KB
- references/codex-engine.md 4.1 KB
- references/error-handling.md 2.1 KB
- references/execution-flow.md 3.6 KB
- references/parallel-execution.md 2.8 KB
- references/review-loop.md 3.7 KB
- references/scope-dialog.md 2.9 KB
- references/session-management.md 1.7 KB
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.
- 6d ago First seen · 228 lines · 91 tokens per session scan B 76db907ad100
work is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 91 tokens to every session and 2,361 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.