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/plans-management/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/plans-management)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/plans-management"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/plans-management.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.00050 | $0.01817 |
| Opus 5 | $0.00025 | $0.00908 |
| Sonnet 5 | $0.00010 | $0.00363 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
plans-management 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 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.
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 — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plans Management Skill
Plans.md のタスク管理とマーカー運用を行うスキル。
トリガーフレーズ
このスキルは以下のフレーズで起動します：
- 「タスクを追加して」
- 「Plans.md を更新して」
- 「完了マークをつけて」
- 「タスクの状態を変更して」
- "add a task"
- "update plans"
- "mark as complete"
概要
このスキルは Plans.md の編集・更新を支援します。 タスクの追加、状態変更、アーカイブを一貫したフォーマットで行います。
Plans.md の構造
# Plans.md - タスク管理
> **最終更新**: YYYY-MM-DD HH:MM
> **更新者**: Claude Code / PM（Cursor/PM Claude）
---
## 🔴 進行中のタスク
- [ ] タスク名 `cc:WIP`
- 詳細説明
- 関連ファイル: `path/to/file.ts`
---
## 🟡 未着手のタスク
- [ ] タスク名 `cc:TODO`
- [ ] タスク名 `pm:依頼中`（互換: cursor:依頼中）
---
## 🟢 完了タスク
- [x] タスク名 `pm:確認済` (YYYY-MM-DD)
---
## 📦 アーカイブ
<!-- 古い完了タスクはここに移動 -->
マーカー運用ルール
状態変更のルール
| 変更 | 実行者 | 条件 |
|---|---|---|
pm:依頼中（互換: cursor:依頼中） → cc:WIP |
Claude Code | タスク着手時 |
cc:TODO → cc:WIP |
Claude Code | タスク着手時 |
cc:WIP → cc:完了 |
Claude Code | 作業完了時 |
cc:完了 → pm:確認済（互換: cursor:確認済） |
PM | レビュー完了時 |
* → blocked |
どちらでも | ブロック発生時 |
マーカーのフォーマット
# 正しい例
- [ ] タスク名 `cc:WIP`
- [x] タスク名 `cc:完了` (2024-01-15)
# 間違った例
- [ ] タスク名 cc:WIP # バッククォートなし
- [ ] タスク名 `cc: WIP` # スペースあり
タスク操作
タスクの追加
## 追加前
## 🟡 未着手のタスク
- [ ] 既存タスク `cc:TODO`
## 追加後
## 🟡 未着手のタスク
- [ ] 既存タスク `cc:TODO`
- [ ] 新規タスク `cc:TODO`
- 詳細説明（あれば）
タスクの状態変更
## 変更前
- [ ] タスク名 `cc:TODO`
## 変更後
- [ ] タスク名 `cc:WIP`
タスクの完了
## 変更前
- [ ] タスク名 `cc:WIP`
## 変更後
- [x] タスク名 `cc:完了` (2024-01-15)
タスクのアーカイブ
完了から 7日以上経過したタスクはアーカイブセクションに移動：
## 📦 アーカイブ
### 2024年1月
- [x] タスク1 `pm:確認済` (2024-01-10)
- [x] タスク2 `pm:確認済` (2024-01-08)
自動整形ルール
Plans.md を更新する際は以下を遵守：
- 最終更新を必ず記載: ヘッダーの日時を更新
- セクション順序を維持: 進行中 → 未着手 → 完了 → アーカイブ
- 空セクションは残す: タスクがなくてもセクションヘッダーは削除しない
- インデントを統一: 2スペースまたは4スペース
便利なパターン
サブタスク
- [ ] 親タスク `cc:WIP`
- [x] サブタスク1
- [ ] サブタスク2
- [ ] サブタスク3
ブロック理由の記載
- [ ] タスク名 `blocked`
- ブロック理由: API キーの発行待ち
- 担当: @username
- 期限: 2024-01-20
What ships with it
8 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.
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 · 239 lines · 50 tokens per session scan A 8257675dbeb1
plans-management is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 50 tokens to every session and 1,817 once invoked, about $0.0003 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
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.