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/workflow-guide/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/workflow-guide)<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/workflow-guide"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/workflow-guide.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.00051 | $0.01474 |
| Opus 5 | $0.00026 | $0.00737 |
| Sonnet 5 | $0.00010 | $0.00295 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
workflow-guide 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow Guide Skill
Cursor ↔ Claude Code 2エージェントワークフローのガイダンスを提供するスキル。
トリガーフレーズ
このスキルは以下のフレーズで起動します：
- 「ワークフローについて教えて」
- 「Cursor との連携方法は？」
- 「作業の流れを教えて」
- 「どうやって進めればいい？」
- "how does the workflow work?"
- "explain 2-agent workflow"
概要
このスキルは、Cursor（PM）と Claude Code（Worker）の役割分担と連携方法を説明します。
2エージェントワークフロー
役割分担
| エージェント | 役割 | 責務 |
|---|---|---|
| Cursor | PM（プロジェクトマネージャー） | タスク割り当て、レビュー、本番デプロイ判断 |
| Claude Code | Worker（作業者） | 実装、テスト、CI修正、staging デプロイ |
ワークフロー図
┌─────────────────────────────────────────────────────────┐
│ Cursor (PM) │
│ ・タスクを Plans.md に追加 │
│ ・Claude Code に作業を依頼（/handoff-to-claude） │
│ ・完了報告をレビュー │
│ ・本番デプロイの判断 │
└─────────────────────┬───────────────────────────────────┘
│ タスク依頼
▼
┌─────────────────────────────────────────────────────────┐
│ Claude Code (Worker) │
│ ・/work でタスク実行（並列実行対応） │
│ ・実装 → テスト → コミット │
│ ・CI 失敗時は自動修正（3回まで） │
│ ・/handoff-to-cursor で完了報告 │
└─────────────────────┬───────────────────────────────────┘
│ 完了報告
▼
┌─────────────────────────────────────────────────────────┐
│ Cursor (PM) │
│ ・変更内容を確認 │
│ ・staging 動作確認 │
│ ・本番デプロイ実行（承認後） │
└─────────────────────────────────────────────────────────┘
Plans.md によるタスク管理
マーカー一覧
| マーカー | 意味 | 設定者 |
|---|---|---|
pm:依頼中 |
PM から依頼（互換: cursor:依頼中） | PM（Cursor/PM Claude） |
cc:TODO |
Claude Code 未着手 | どちらでも |
cc:WIP |
Claude Code 作業中 | Claude Code |
cc:完了 |
Claude Code 完了 | Claude Code |
pm:確認済 |
PM 確認完了（互換: cursor:確認済） | PM（Cursor/PM Claude） |
cursor:依頼中 |
（互換）pm:依頼中 と同義 | Cursor |
cursor:確認済 |
（互換）pm:確認済 と同義 | Cursor |
blocked |
ブロック中 | どちらでも |
What ships with it
4 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 · 165 lines · 51 tokens per session scan A b374edd806c4
workflow-guide is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,474 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…