harness-diagnostics AGENTS.md

A set of instructions for coding agents working on the harness-diagnostics repository. It explains the repository's roles, development workflow, synchronization, and required verification scripts.

In plain words
What is it for?
Use it when modifying harness-diagnostics, running its audits, or syncing the repository with its installed Codex skill.
Why use it?
It gives agents the project-specific rules needed to make, check, and synchronize changes correctly.

Instructions file for CodexOpenCode

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.

agentmods
npx agentmods add instructions/junh0328/harness-diagnostics/agents-md
Clone the repo
git clone --depth 1 https://github.com/junh0328/harness-diagnostics

Made for: Codex, OpenCode.

Per session 664 This file is loaded in full into every session.
When invoked 664 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.00664 $0.00664
Opus 5 $0.00332 $0.00332
Sonnet 5 $0.00133 $0.00133
Haiku 4.5 $0.00066 $0.00066

Measured 3d ago against content hash 8645840138af, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

harness-diagnostics AGENTS.md 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 3d 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.

AGENTS.md · 53 lines

What it actually says

GitHub 레포지토리용 AGENTS

이 문서는 harness-diagnostics GitHub 레포지토리를 수정하는 에이전트를 위한 운영 가이드다. 스킬 런타임 지침은 SKILL.md, 사람용 설명은 README.md를 기준으로 본다.

역할

  • 이 standalone 레포는 harness-diagnostics의 source of truth다.
  • $HOME/.codex/skills/harness-diagnostics는 배포 대상 복사본이며 직접 수정하지 않는다.
  • 이 문서는 GitHub 레포지토리 운영용이다. issue, PR, CI, release sync 같은 저장소 작업 규칙을 다룬다.

시작 순서

  • 스킬 런타임 계약은 SKILL.md에서 확인한다.
  • 로컬 작업 전 .nvmrc 기준으로 Node 20을 맞추고 bash scripts/install-hooks.sh로 local pre-commit을 설치한다.
  • 검증과 self 로그 운영 규칙은 references/verification-workflow.md에서 확인한다.
  • 릴리즈와 동기화 흐름은 README.md의 설치/동기화 및 버전 관리 섹션을 따른다.

작업 규칙

  • SKILL.md는 짧고 map 지향적으로 유지하고, 상세 설명은 references/, examples/, scripts/로 내린다.
  • 새 runtime 파일을 추가하면 SKILL.md, README.md, scripts/sync-to-codex.sh를 함께 갱신한다.
  • 의미 있는 변경 뒤에는 반드시 로컬 검증을 수행하고 logs/self-audit-log.mdskill-self 요약을 남긴다.
  • GitHub 템플릿과 workflow를 수정하면 .codex 복사본에서도 같은 self-audit가 통과하는지 확인한다.

필수 검증

레포 루트에서 아래 명령을 실행한다.

bash scripts/check-node-version.sh
bash scripts/self-audit.sh
bash scripts/maintenance-scan.sh
bash scripts/adversarial-verify.sh
bash scripts/semantic-verify.sh
bash scripts/behavioral-verify.sh
node scripts/calculate-score.js references/score-template.json

릴리즈 동작이나 sync manifest를 수정했으면 아래도 실행한다.

bash scripts/release-sync.sh

릴리즈 절차

  1. 문서, 스크립트, 템플릿을 함께 갱신한다.
  2. SKILL.md version과 CHANGELOG.md를 업데이트한다.
  3. 검증 명령을 실행한다.
  4. self 점수와 변경 메모를 logs/self-audit-log.md에 기록한다.
  5. 브랜치에서 커밋하고 PR을 생성한 뒤 체크 통과 후 머지한다.
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. 3d ago First seen · 53 lines · 664 tokens per session scan A 8645840138af

Subscribe to this mod's changes

harness-diagnostics AGENTS.md is an instructions file published in the GitHub repository junh0328/harness-diagnostics (11 stars, last pushed 5mo ago), licensed MIT. It adds 664 tokens to every session, about $0.0033 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.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens