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/backpaper0/claude-code-in-devcontainer-example/commit-by-logical-unitsnpx skills add backpaper0/claude-code-in-devcontainer-example --skill commit-by-logical-unitsgit clone --depth 1 https://github.com/backpaper0/claude-code-in-devcontainer-exampleWhat 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.00033 | $0.00700 |
| Opus 5 | $0.00016 | $0.00350 |
| Sonnet 5 | $0.00007 | $0.00140 |
| Haiku 4.5 | $0.00003 | $0.00070 |
Grade A, and why
commit-by-logical-units 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 2d 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.
What it actually says
現在の変更内容を確認し、論理的に意味がある単位で複数のコミットに分けて実行してください。
以下の手順で実行してください：
-
変更内容の確認
git statusで変更されたファイルを確認git diff --statで変更の統計情報を確認git log --oneline -10で最近のコミット履歴を確認し、コミットメッセージのスタイルを把握
-
変更内容の分析
- いくつかの代表的なファイルの差分を確認（
git diff [ファイルパス] | head -50） - 変更の性質を理解し、論理的なグループに分類
- 例：
- ルートディレクトリのファイル
- 機能別のドキュメント（features, getting-started, recipes, tools, publishingなど）
- 設定ファイル
- テストファイル
- ソースコード（機能ごと、モジュールごと）
- いくつかの代表的なファイルの差分を確認（
-
論理的な単位でコミット
- 各グループごとに
git add [ファイル/ディレクトリ]とgit commitを実行 - コミットメッセージは英語で簡潔に記述
- コミットメッセージの形式：
git commit -m "$(cat <<'EOF' 変更の概要を1行で記述 詳細な説明（必要に応じて） Co-Authored-By: Claude Sonnet 4.5 <[email protected]> EOF )"
- 各グループごとに
-
コミット後の確認
git statusで残りの変更を確認git log --oneline -10でコミット履歴を確認
重要な原則
- 論理的な単位: 関連する変更を1つのコミットにまとめる
- 簡潔なメッセージ: 何を変更したかを明確に記述
- 英語で記述: コミットメッセージは英語で書く
- 複数コミット推奨: 大きな変更は複数のコミットに分ける
- 意味のあるグループ化: ディレクトリ構造や機能に基づいてグループ化
除外すべきファイル
以下のファイルは通常コミットしない：
.envファイル（環境変数、機密情報）node_modules/（依存関係）- ビルド成果物
これらのファイルが変更されている場合は、ユーザーに確認するか、無視してください。
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.
- 2d ago First seen · 60 lines · 33 tokens per session scan A c72305650a42
commit-by-logical-units is a skill published in the GitHub repository backpaper0/claude-code-in-devcontainer-example (5 stars, last pushed 6mo ago), licensed MIT. It adds 33 tokens to every session and 700 once invoked, about $0.0002 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.