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 agentmods add skills/chachamaru127/codex-harness/breezingnpx skills add Chachamaru127/codex-harness --skill breezinggit 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/breezing)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/breezing"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/breezing.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 | $0.00080 | $0.02455 |
| Opus 5 | $0.00040 | $0.01228 |
| Sonnet 5 | $0.00016 | $0.00491 |
| Haiku 4.5 | $0.00008 | $0.00246 |
Grade A, and why
breezing 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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Breezing Skill
Agent Teams を活用して Plans.md の未完了タスクをチーム協調で完全自動完走する。
Philosophy
「Lead は指揮するだけ、手を動かすのは Teammate」
delegate mode で Lead は調整に専念。 実装は Implementer、レビューは Reviewer。三者分離の完全自律。
Quick Reference
/breezing # スコープを聞いてから実行
/breezing all # Plans.md 全タスクを完走
/breezing 3-6 # タスク3〜6を完走
/breezing 認証機能からユーザー管理まで # 自然言語で範囲指定
/breezing --codex all # Codex MCP で全タスク完走
/breezing --codex --parallel 2 ログイン機能 # Codex 2並列で範囲指定
/breezing --parallel 2 ログイン機能 # Claude 2並列で範囲指定
/breezing 続きやって # 前回中断から再開
Options
| Option | Description | Default |
|---|---|---|
all |
全未完了タスクを対象 | - |
N or N-M |
タスク番号/範囲指定 | - |
--codex |
Codex MCP で実装委託 | false (Claude 実装) |
--parallel N |
Implementer 並列数 | auto |
--no-commit |
自動コミット抑制 | false |
Scope Dialog (引数なし時)
引数なしで呼ぶと、対話でスコープを確認:
/breezing
どこまでやりますか?
1) 全部 (推奨): 残りのタスクを全て完走
2) 指定: タスク番号や範囲を指定 (例: 3, 3-6)
> [Enter = 1]
引数ありなら即実行（対話スキップ）:
/breezing all # 全タスク即実行
/breezing 3-6 # 範囲即実行
/work との違い
| 特徴 | /work |
/breezing |
|---|---|---|
| 並列手段 | Task tool (サブエージェント) | Agent Teams (Teammates) |
| Lead の役割 | 調整+実装 | delegate (調整専念) |
| レビュー | Lead 自己レビュー | 独立 Reviewer Teammate |
| リテイク | 自動 (Lead 自己修正) | 自動 (Lead 分解 → Impl 修正) |
| デフォルトスコープ | 次のタスク | 全部 |
| コスト | 低〜中 | 高 |
--codex Engine
--codex フラグで Codex MCP にすべての実装を委託:
| 項目 | デフォルト | --codex |
|---|---|---|
| Implementer | task-worker (Claude) | codex-implementer (Codex MCP) |
| 実装の仕組み | Sonnet が直接コーディング | Codex MCP 経由で委託 |
| 品質保証 | セルフレビュー 4 観点 | AGENTS_SUMMARY + Quality Gates |
| ファイル分離 | owns: アノテーション | Lead 判断（worktree or owns:） |
| コスト特性 | Claude トークン消費 | Codex API + Claude レビュー |
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 365 B
- references/CLAUDE.md 2.3 KB
- references/codex-engine.md 7.0 KB
- references/codex-review-integration.md 5.0 KB
- references/execution-flow.md 16 KB
- references/guardrails-inheritance.md 13 KB
- references/plans-to-tasklist.md 6.2 KB
- references/review-retake-loop.md 12 KB
- references/session-resilience.md 12 KB
- references/team-composition.md 13 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.
- 4d ago First seen · 189 lines · 80 tokens per session scan A a6041f6b4c5a
breezing is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 80 tokens to every session and 2,455 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…