working-context

working-context is a command for Claude Code from s977043/PlanGate. It costs 0 tokens per session (787 once invoked), scanned A, original, MIT.

A command for saving and restoring the working context of a tracked task. It reads or updates files containing the task status, plan, remaining work, pull requests, and changes made.

In plain words
What is it for?
Use it to list tracked tasks, start or reopen a task, create its working files, or save the current task status before stopping.
Why use it?
It helps work continue across sessions without losing the current state, unfinished tasks, or changes from the original plan.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions Claude Code.

Good fit Use it to list tracked tasks, start or reopen a task, create its working files, or save the current task status before stopping.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/s977043/plangate/working-context
Install

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.

Clone the repo
git clone --depth 1 https://github.com/s977043/PlanGate

Made for: Claude Code.

Wrote 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.

agentmods badge for working-context

README.md
[![agentmods](https://agentmods.dev/badge/commands/s977043/plangate/working-context/github.svg)](https://agentmods.dev/commands/s977043/plangate/working-context)
Your own site
<a href="https://agentmods.dev/commands/s977043/plangate/working-context"><img src="https://agentmods.dev/badge/commands/s977043/plangate/working-context/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.

agentmods 80×15 button for working-context

Your own site · 80×15
<a href="https://agentmods.dev/commands/s977043/plangate/working-context"><img src="https://agentmods.dev/badge/commands/s977043/plangate/working-context.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00787
Opus 5.5 $0.00000 $0.00315
Sonnet 5.5 $0.00000 $0.00157
Haiku 4.5 $0.00000 $0.00079

Measured 1mo ago against content hash e8bcca3d046f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

working-context 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 1mo 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.

.claude/commands/working-context.md · 66 lines

What it actually says

/working-context

チケット作業の開始・再開・中断時に、作業コンテキストを管理する。

ルール詳細: .claude/rules/working-context.md

引数

$ARGUMENTS に以下のいずれかが渡される:

  • TASK-XXXX — チケット番号(新規作成 or 既存読み込み)
  • save — 現在作業中のチケットのstatus.mdを更新
  • 引数なし — docs/working/ 配下の一覧を表示

実行フロー

1. 引数解析

引数を解析し、以下のいずれかのモードを決定する:

  • 一覧表示モード: 引数なし → docs/working/ 配下のディレクトリ一覧と各status.mdの先頭5行を表示
  • 読み込みモード: TASK-XXXX が渡され、かつ docs/working/TASK-XXXX/ が存在する
  • 新規作成モード: TASK-XXXX が渡され、かつ docs/working/TASK-XXXX/ が存在しない
  • 保存モード: save が渡された

2. 読み込みモード(セッション開始・再開)

以下のファイルを順に読み、現在の状態をユーザーに報告する:

  1. docs/working/TASK-XXXX/status.md を読む
  2. docs/working/TASK-XXXX/plan.md を読む(存在すれば)
  3. docs/working/TASK-XXXX/todo.md を読む(存在すれば)

報告内容:

  • PR一覧と各PRの状態
  • 残タスク一覧
  • 計画からの変更点
  • 次のアクション候補

3. 新規作成モード

  1. docs/working/TASK-XXXX/ ディレクトリを作成
  2. ユーザーに以下を確認:
    • 外部チケットURL(任意)
    • PBIの概要(Why / What)
  3. docs/working/TASK-XXXX/status.md をテンプレートとしてコピーし、チケット番号・PBI情報を埋めて生成する

4. 保存モード(セッション中断・終了)

  1. 現在のgitブランチを確認し、対応するチケット番号を特定(TASK-XXXX を含まないブランチ名の場合はユーザーにチケット番号を尋ねる)
  2. docs/working/TASK-XXXX/status.md を読み込む
  3. 以下を更新:
    • 最終更新日
    • PR一覧の状態(gh pr list やgit logで確認)
    • コミット履歴(ブランチ固有のコミットを追記)
    • 残タスクのチェック状態
    • 計画からの変更点(作業中に発生した差分)
    • Claude Codeプロンプト(次回作業用のプロンプトを整備)
  4. 更新内容をユーザーに報告

重要ルール

  • 第1原則を遵守: ファイル生成・更新前にユーザー確認を取る
  • status.md の更新は差分が分かる形で報告する
  • 外部チケットURLが分かる場合は参照リンクとしてコンテキストに記録する
Changes

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.

  1. 1mo ago First seen · 66 lines · 0 tokens per session scan A e8bcca3d046f

Subscribe to this mod's changes

working-context is a command published in the GitHub repository s977043/PlanGate (2 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 787 tokens. 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-09-03.