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 skills add MH4GF/claude-code --skill workpadgit clone --depth 1 https://github.com/MH4GF/claude-codeWrote 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/mh4gf/claude-code/workpad)<a href="https://agentmods.dev/skills/mh4gf/claude-code/workpad"><img src="https://agentmods.dev/badge/skills/mh4gf/claude-code/workpad/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/mh4gf/claude-code/workpad"><img src="https://agentmods.dev/badge/skills/mh4gf/claude-code/workpad.svg" alt="Reviewed on agentmods" width="80" 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.00105 | $0.01614 |
| Opus 5.5 | $0.00042 | $0.00646 |
| Sonnet 5.5 | $0.00021 | $0.00323 |
| Haiku 4.5 | $0.00011 | $0.00161 |
Grade A, and why
workpad 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 2mo 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workpad
バックグラウンドセッションが issue へ集約する作業ノート用コメントを管理するスキル。
issue ごとに ## Codex Workpad コメントを 1 つだけ維持する。再開時は同じコメントを読み直して作業を継続する。
Tracker の判定
操作先は tracker ごとに違う。作業中の repo の WORKFLOW.md frontmatter tracker.kind を読んで分岐する。works repo のみ agents/ai-native/WORKFLOW.md、それ以外は repo root の WORKFLOW.md に置かれている。読み取れない場合は linear として扱う。
以降の手順は tracker 共通の骨格で、具体的な操作だけを Tracker 別操作から引く。
前提
- 対象 issue identifier (
kind: linearならMH-40、kind: githubなら#123) が文脈から既知 kind: linearは Linear MCP、kind: githubはghが利用可能
スコープ外
- 別コメントへの分割書き込み。1 issue 1 ワークパッドで固定し、節ごとに別コメントを作らない
- 他人のコメントへの上書き。自分が作成したコメントのみ再利用する
手順
1. 既存ワークパッドを探す
対象 issue のコメント一覧を取得し、次の条件をすべて満たすコメントを探す。
bodyが## Codex Workpadで始まる- 作成者が自分自身
- (
kind: linearのみ) 未 resolve である。resolved は人間が意図的に閉じた印として扱い、再利用せず新規作成する
複数該当した時は最新の 1 件を採用し、残りを後段で言及せず放置する (履歴として保つ)。
2a. 既存ワークパッドを更新する
該当コメントが見つかった場合、そのコメント ID を指定して本文を上書きする。
更新内容は「直近の進捗」+「次に取る行動」を反映する。env stamp 行は再生成して上書きする (短い SHA や cwd が変わるため)。
2b. 新規ワークパッドを作成する
該当コメントが無い場合、下記テンプレに沿って本文を作り、issue へコメントを投稿する。
## Codex Workpad
<env-stamp>
### Plan
- [ ] step 1
- [ ] step 2
### Acceptance Criteria
- ...
### Validation
- 実行コマンドと結果
### Notes
- 設計判断のメモ
### Confusions
- 詰まったポイント、確認したい点
<env-stamp> を host:abs-workdir@short-sha 形式で書く。例: mac-studio:/Users/hermes/ghq/github.com/MH4GF/claude-code@7cf89d5。
- ホスト名を
hostname -sから取得 - ワーキングディレクトリ絶対パスを
pwdから取得 - 短い SHA を
git rev-parse --short HEADから取得
Tracker 別操作
kind: linear
| 操作 | 手段 |
|---|---|
| issue ID 解決 | Linear MCP の issue 取得ツールを identifier で呼び id (UUID) を得る。以降の呼び出しはこの UUID を使う |
| 自分の識別 | Linear MCP の自身ユーザー取得ツールで得たアカウントと、コメントの user を突き合わせる |
| コメント一覧 | Linear MCP のコメント一覧取得ツールを issue ID 指定で呼ぶ。resolvedAt が null のものだけ再利用対象 |
| 更新 | Linear MCP のコメント保存ツールを id 指定で呼び本文を上書きする |
| 新規作成 | Linear MCP のコメント保存ツールを issue 指定で呼ぶ |
kind: github
identifier #123 の 123 が issue number。<repo> は WORKFLOW.md の tracker.repo (owner/name)。
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.
- 2mo ago First seen · 123 lines · 105 tokens per session scan A 33a86fa77f92
workpad is a skill published in the GitHub repository MH4GF/claude-code (2 stars, last pushed 5d ago), licensed MIT. It adds 105 tokens to every session and 1,614 once invoked, about $0.0004 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.