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/chachamaru127/claude-code-harness/cinpx skills add Chachamaru127/claude-code-harness --skill cigit clone --depth 1 https://github.com/Chachamaru127/claude-code-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/claude-code-harness/ci)<a href="https://agentmods.dev/skills/chachamaru127/claude-code-harness/ci"><img src="https://agentmods.dev/badge/skills/chachamaru127/claude-code-harness/ci.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 | $0.00048 | $0.01823 |
| Opus 5 | $0.00024 | $0.00911 |
| Sonnet 5 | $0.00010 | $0.00365 |
| Haiku 4.5 | $0.00005 | $0.00182 |
Grade A, and why
ci 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 4d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ci — 92% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 197 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CI/CD Skills
CI/CD パイプラインに関する問題を解決するスキル群です。
発動条件
- 「CIが落ちた」「GitHub Actionsが失敗」
- 「ビルドエラー」「テストが通らない」
- 「パイプラインを直して」
機能詳細
| 機能 | 詳細 | トリガー |
|---|---|---|
| 失敗分析 | See references/analyzing-failures.md | 「ログを見て」「原因を調べて」 |
| テスト修正 | See references/fixing-tests.md | 「テストを直して」「修正案を出して」 |
実行手順
- テスト vs 実装判定（Step 0）
- ユーザーの意図を分類（分析 or 修正）
- 複雑度を判定（下記参照）
- 上記の「機能詳細」から適切な参照ファイルを読む、または ci-cd-fixer サブエージェント起動
- 結果を確認し、必要に応じて再実行
Step 0: テスト vs 実装判定（品質判定ゲート）
CI 失敗時、まず原因の切り分けを行う:
CI 失敗報告
↓
┌─────────────────────────────────────────┐
│ テスト vs 実装判定 │
├─────────────────────────────────────────┤
│ エラーの原因を分析: │
│ ├── 実装が間違い → 実装を修正 │
│ ├── テストが古い → ユーザーに確認 │
│ └── 環境問題 → 環境修正 │
└─────────────────────────────────────────┘
禁止事項（改ざん防止）
⚠️ CI 失敗時の禁止事項
以下の「解決策」は禁止です：
| 禁止 | 例 | 正しい対応 |
|------|-----|-----------|
| テスト skip 化 | `it.skip(...)` | 実装を修正 |
| アサーション削除 | `expect()` を消す | 期待値を確認 |
| CI チェック迂回 | `continue-on-error` | 根本原因修正 |
| lint ルール緩和 | `eslint-disable` | コードを修正 |
判断フロー
🔴 CI が失敗しています
**判断が必要です**:
1. **実装が間違い** → 実装を修正 ✅
2. **テストの期待値が古い** → ユーザーに確認を求める
3. **環境の問題** → 環境設定を修正
⚠️ テストの改ざん（skip化、アサーション削除）は禁止です
どれに該当しますか？
承認が必要な場合
テスト/設定の変更がやむを得ない場合:
## 🚨 テスト/設定変更の承認リクエスト
### 理由
[なぜこの変更が必要か]
### 変更内容
[差分]
### 代替案の検討
- [ ] 実装の修正で解決できないか確認した
ユーザーの明示的な承認を待つ
Git log 拡張フラグの活用（CC 2.1.49+）
CI 失敗時の原因コミット特定に構造化ログを活用します。
原因コミットの特定
# 構造化フォーマットでコミット分析
git log --format="%h|%s|%an|%ad" --date=short -10
# トポロジカル順序で時系列分析
git log --topo-order --oneline -20
# 変更ファイルと原因の紐付け
git log --raw --oneline -5
主な活用場面
| 用途 | フラグ | 効果 |
|---|---|---|
| 失敗原因の特定 | `--format="%h | %s"` |
| 時系列での追跡 | --topo-order |
マージ順序を考慮した追跡 |
| 変更影響の把握 | --raw |
ファイル変更の詳細表示 |
| マージ除外分析 | --cherry-pick --no-merges |
実コミットのみを抽出 |
What ships with it
2 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.
- 4d ago First seen · 197 lines · 48 tokens per session scan A 40862647b100
ci is a skill published in the GitHub repository Chachamaru127/claude-code-harness (3,081 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,823 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-30.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…