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 instructions/ryne2010/harness-engineering-audit/agents-mdgit clone --depth 1 https://github.com/ryne2010/harness-engineering-auditWrote 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/instructions/ryne2010/harness-engineering-audit/agents-md)<a href="https://agentmods.dev/instructions/ryne2010/harness-engineering-audit/agents-md"><img src="https://agentmods.dev/badge/instructions/ryne2010/harness-engineering-audit/agents-md.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.00288 | $0.00288 |
| Opus 5 | $0.00144 | $0.00144 |
| Sonnet 5 | $0.00058 | $0.00058 |
| Haiku 4.5 | $0.00029 | $0.00029 |
Grade A, and why
harness-engineering-audit 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 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.
What it actually says
AGENTS.md
This repo packages the harness-engineering-audit Codex skill.
Operating Map
- Source skill payload:
skills/harness-engineering-audit/ - Plugin mirror payload:
plugins/harness-engineering-audit/skills/harness-engineering-audit/ - Smoke test:
tests/smoke/run_skill_smoke.py - Mirror parity check:
tests/check_skill_mirror.py - User docs:
README.mdanddocs/ - Generated audit output:
.codex/reports/harness-engineering-audit/
Development Rules
- Keep the source skill and plugin mirror in sync.
- Do not add dependencies for validation or packaging unless explicitly requested.
- Keep audit mode report-only; setup modes must remain explicit and bounded.
- Keep user-scope and project-scope install examples distinct.
- Prefer small, reversible patches over broad rewrites.
Validation
Run before claiming completion:
make validate
make validate compiles Python scripts, checks plugin mirror parity, and runs the smoke suite.
Docs Authority
docs/README.mdis the docs index.docs/USAGE.mdis the user workflow reference.docs/INSTALL.mdis the install/update reference.docs/HARNESS_ENGINEERING_SOURCE_SYNTHESIS.mdrecords source concepts and synthesis.
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 · 38 lines · 288 tokens per session scan A 17f6454b0084
harness-engineering-audit AGENTS.md is an instructions file published in the GitHub repository ryne2010/harness-engineering-audit (5 stars, last pushed 3mo ago), licensed MIT. It adds 288 tokens to every session, about $0.0014 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 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).
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.
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.
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.
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).
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.