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 jh941213/codex-lattice --skill harness-diagnosticsgit clone --depth 1 https://github.com/jh941213/codex-latticeWrote 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/jh941213/codex-lattice/harness-diagnostics)<a href="https://agentmods.dev/skills/jh941213/codex-lattice/harness-diagnostics"><img src="https://agentmods.dev/badge/skills/jh941213/codex-lattice/harness-diagnostics.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.1 | $0.00062 | $0.01605 |
| Opus 5 | $0.00031 | $0.00803 |
| Sonnet 5 | $0.00012 | $0.00321 |
| Haiku 4.5 | $0.00006 | $0.00161 |
Grade A, and why
harness-diagnostics 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 8d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Diagnostics — 에이전트 하네스 자가 진단 스킬
12원칙 기반 하네스 성숙도 진단 및 개선 제안 도구. Read-only: 진단 + 제안만 수행하며, 직접 파일을 수정하지 않음.
입력
$ARGUMENTS
모드 판별
| 모드 | 트리거 키워드 | 목적 |
|---|---|---|
| Setup | "환경 구축", "setup", "초기화" | 에이전트 협업 환경 초기 점검 + 추천 |
| Audit | "하네스 진단", "점검", "audit", 기본값 | 12원칙 점수화 + 개선 로드맵 |
| Maintenance | "drift 확인", "정리", "maintenance" | stale 코드/문서 감지 + 정리 제안 |
키워드가 없으면 Audit 모드를 기본으로 실행.
12원칙 점수 체계
각 원칙 0-8점, 총 100점 (12 × 8 = 96, 나머지 4점은 종합 보너스).
| # | 원칙 | 점검 대상 |
|---|---|---|
| 1 | Agent Entry Point | AGENTS.md 존재 + 명확한 에이전트 진입점 |
| 2 | Map, Not Manual | 문서가 "지도"인가 vs "매뉴얼"인가 (포인터, 계층 구조) |
| 3 | Invariant Enforcement | 도구가 실수를 자동 차단하는가 (hooks, linters, CI) |
| 4 | Convention Over Configuration | 명시적 규칙 파일 존재 (rules/, .eslintrc, prettier 등) |
| 5 | Progressive Disclosure | 정보 계층화 (AGENTS.md → rules/ → docs/ → 코드) |
| 6 | Layered Architecture | 의존성 방향 단방향, 레이어 분리 |
| 7 | Garbage Collection | stale 파일/문서/의존성 정리 메커니즘 |
| 8 | Observability | 자체 검증 가능 (테스트, 빌드, 타입체크) |
| 9 | Knowledge in Repo | 지식이 레포에 있는가 (ADR, docs/, 인라인 설명) |
| 10 | Reproducibility | 동일 입력 → 동일 결과 (lock 파일, 환경 설정) |
| 11 | Modularity | 변경 영향 예측 가능 (모듈 경계, 인터페이스) |
| 12 | Self-Documentation | 코드가 의도를 설명하는가 (네이밍, 구조) |
성숙도 등급
| 등급 | 점수 | 설명 |
|---|---|---|
| L1 None | 0-19 | 하네스 없음. 에이전트가 매번 처음부터 추론 |
| L2 Basic | 20-39 | 기본 설정 존재. 일부 자동화 |
| L3 Structured | 40-59 | 구조화된 규칙과 도구. 대부분 자동화 |
| L4 Optimized | 60-79 | 최적화된 하네스. 에이전트 자율성 높음 |
| L5 Autonomous | 80-100 | 자율 운영. 자가 진단/수정 가능 |
실행 절차
Setup 모드
- 프로젝트 루트 탐색 (
rg,find,ls등 읽기 전용 명령) - 다음 항목 존재 여부 확인:
AGENTS.mdrules/.codex/config.toml.codex/agents/*.tomldocs/디렉토리- 패키지 매니저 lock 파일
- 린터/포매터 설정
- 테스트 프레임워크 설정
- CI/CD 설정
- 누락된 항목에 대해 생성 추천 (직접 생성하지 않음)
- 추천 우선순위: P0 (즉시) → P1 (권장) → P2 (개선)
Audit 모드
- 12원칙 각각에 대해 점검 실행:
- 파일/디렉토리 존재 여부 (Glob)
- 설정 파일 내용 분석 (Read)
- 패턴 검색 (Grep)
- 원칙별 점수 산정 (0-8)
- 종합 보너스 산정 (0-4):
- 원칙 간 시너지 (예: hooks + rules + docs 3개 모두 있으면 +2)
- 일관성 (네이밍 규칙, 구조 통일성 +2)
- 리포트 출력
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.
- 8d ago First seen · 157 lines · 62 tokens per session scan A 552446aba2eb
harness-diagnostics is a skill published in the GitHub repository jh941213/codex-lattice (19 stars, last pushed 3mo ago), licensed MIT. It adds 62 tokens to every session and 1,605 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.