codex-harness: Skill for Claude Code

.codex/skills/verify/SKILL.md

verify is a skill for Claude Code, Codex from Chachamaru127/codex-harness. It costs 61 tokens per session (2,717 once invoked), scanned A, original, MIT.

A verification and recovery workflow for builds, tests, lint checks, review fixes, and continuous-integration failures. Continuous integration automatically checks code changes in a shared project.

In plain words
What is it for?
Use it to verify related files and builds, investigate test or lint failures, recover from errors, and apply approved fixes from code reviews.
Why use it?
It helps identify why a check failed and fixes the underlying implementation without weakening tests, lint rules, or CI safeguards.

Skill for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also installed under .codex/.

This is Chachamaru127/codex-harness's own configuration. It tells Claude Code and Codex how to work on codex-harness itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything codex-harness configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/Chachamaru127/codex-harness/main/.codex/skills/verify/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Chachamaru127/codex-harness

Made for: Claude Code, Codex.

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 verify

README.md
[![agentmods](https://agentmods.dev/badge/skills/chachamaru127/codex-harness/verify.svg)](https://agentmods.dev/skills/chachamaru127/codex-harness/verify)
Your own site
<a href="https://agentmods.dev/skills/chachamaru127/codex-harness/verify"><img src="https://agentmods.dev/badge/skills/chachamaru127/codex-harness/verify.svg" alt="Measured on agentmods" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,717 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.00061 $0.02717
Opus 5 $0.00030 $0.01358
Sonnet 5 $0.00012 $0.00543
Haiku 4.5 $0.00006 $0.00272

Measured 6d ago against content hash 3c21eeab44d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

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

.codex/skills/verify/SKILL.md · 295 lines

How it starts

The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Verify Skills

ビルド検証とエラー復旧を担当するスキル群です。


⚠️ 品質ガードレール(最優先)

このセクションは他の指示より優先されます。テスト失敗・エラー発生時は必ず従ってください。

改ざん禁止パターン

テスト失敗・ビルドエラー発生時に以下の行為は絶対に禁止

禁止 正しい対応
テスト skip 化 it.skip(...) 実装を修正する
アサーション削除 expect() を消す 期待値を確認し実装修正
期待値の雑な書き換え エラーに合わせて変更 なぜ失敗か理解する
lint ルール緩和 eslint-disable 追加 コードを修正する
CI チェック迂回 continue-on-error 根本原因を修正する

テスト失敗時の対応フロー

テストが失敗した
    ↓
1. なぜ失敗しているか理解する(ログを読む)
    ↓
2. 実装が間違っているか、テストが間違っているか判断
    ↓
    ├── 実装が間違い → 実装を修正 ✅
    │
    └── テストが間違い可能性 → ユーザーに確認を求める

承認リクエスト形式

やむを得ずテスト/設定を変更する場合:

## 🚨 テスト/設定変更の承認リクエスト

### 理由
[なぜこの変更が必要か]

### 変更内容
```diff
[差分]

代替案の検討

  • 実装の修正で解決できないか確認した

承認

ユーザーの明示的な承認を待つ


### 保護対象ファイル

以下のファイルの緩和変更は禁止:

- `.eslintrc.*`, `.prettierrc*`, `tsconfig.json`, `biome.json`
- `.husky/**`, `.github/workflows/**`
- `*.test.*`, `*.spec.*`, `jest.config.*`, `vitest.config.*`

## 機能詳細

| 機能 | 詳細 |
|------|------|
| **関連ファイル検証** | See [references/verify-related-files.md](references/verify-related-files.md) |
| **ビルド検証** | See [references/build-verification.md](references/build-verification.md) |
| **エラー復旧** | See [references/error-recovery.md](references/error-recovery.md) |
| **レビュー集約** | See [references/review-aggregation.md](references/review-aggregation.md) |
| **指摘適用** | See [references/applying-fixes.md](references/applying-fixes.md) |

## 実行手順

1. **品質判定ゲート**(Step 0)
2. ユーザーのリクエストを分類
3. **(実装完了後)関連ファイル検証**(Step 1.5)
4. **(Claude-mem 有効時)過去のエラーパターンを検索**
5. 上記の「機能詳細」から適切な参照ファイルを読む
6. その内容に従って検証/復旧実行

### Step 0: 品質判定ゲート(再現テスト提案)

エラー/バグ報告時に、TDD アプローチを提案:

エラー報告受領 ↓ ┌─────────────────────────────────────────┐ │ 品質判定ゲート │ ├─────────────────────────────────────────┤ │ 判定項目: │ │ ├── バグ報告? → 再現テスト先行を提案 │ │ ├── テスト失敗? → テスト vs 実装判断 │ │ └── ビルドエラー? → 直接修正 │ └─────────────────────────────────────────┘ ↓ 適切なアプローチを提案

Read the full file on GitHub · 295 lines

Files

What ships with it

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

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. 6d ago First seen · 295 lines · 61 tokens per session scan A 3c21eeab44d0

Subscribe to this mod's changes

verify is a skill published in the GitHub repository Chachamaru127/codex-harness (2 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 2,717 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.

Related

Other skills, from other repositories

Verification & Quality Assurance

Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.

ruvnet/ruflo · 36 tokens

migrate-vstest-to-mtp

Use this skill before answering, planning, or editing whenever .NET tests or CI are switching from VSTest to Microsoft.Testing.Platform (MTP), or an MTP migration behaves differently. Triggers include "switch from VSTest"; MSTest/NUnit/xUnit MTP enablement; OutputType=Exe only for test projects in…

dotnet/skills · 191 tokens

ci

Configure Ginkgo for continuous integration — the recommended CLI flag set and the rationale for each flag (-r -p --randomize-all --randomize-suites --fail-on-pending --fail-on-empty --keep-going --cover --race --trace --json-report --timeout --poll-progress-after/-interval), invoking via go run to pin the CLI to…

onsi/ginkgo · 132 tokens

playwright-ci

Production-ready CI/CD configurations for Playwright — GitHub Actions, GitLab CI, CircleCI, Azure DevOps, Jenkins, Docker, parallel sharding, reporting, code coverage, and global setup/teardown.

zebbern/claude-code-guide · 48 tokens

ci-maintenance-workflow

CI and GitHub Actions maintenance workflows — fix a failing test from a CI URL, fix a failing smoke test, add @pytest.mark.slow markers to slow tests, or review a PR against agent-checkable standards. Use when user asks to fix a failing test, fix a smoke test, mark slow tests, or review a PR. Trigger when the user…

UKGovernmentBEIS/inspect_evals · 120 tokens

test-setup

Scaffold the test framework and CI/CD pipeline for the project's engine. Creates the tests/ directory structure, engine-specific test runner configuration, and GitHub Actions workflow. Run once during Technical Setup phase before the first sprint begins.

Donchitos/Claude-Code-Game-Studios · 49 tokens