Borrowing it
Nothing to install: this file belongs to Pierry/harness-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pierry/harness-kit/main/AGENTS.mdgit clone --depth 1 https://github.com/Pierry/harness-kitWrote 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/pierry/harness-kit/agents-md)<a href="https://agentmods.dev/instructions/pierry/harness-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/pierry/harness-kit/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/pierry/harness-kit/agents-md"><img src="https://agentmods.dev/badge/instructions/pierry/harness-kit/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.03723 | $0.03723 |
| Opus 5.5 | $0.01489 | $0.01489 |
| Sonnet 5.5 | $0.00745 | $0.00745 |
| Haiku 4.5 | $0.00372 | $0.00372 |
Grade C, and why
harness-kit AGENTS.md scanned grade C with 1 finding 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
The installer pre-authorizes these in `settings.json` `permissions.allow` (both bare-path and `bash <path>` forms), so a full pipeline run never stops for a harness-internal prompt. Destructive ops (`rm -rf`, force push, How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md, Agent Registry & Routing
Source of truth for every agent, skill, and runtime path in this workspace.
This file is the declarative spec. Execution lives in .claude/agents/ (definitions), .claude/runtime/ (state, outputs), and .claude/shared/ (cross-agent docs). Pipelines like /sse:run and /product-manager:run consult this registry when dispatching.
Portable across tools (Claude Code, Cursor, Codex CLI, Gemini CLI, and others): all read AGENTS.md at the repo root. See Cross-tool compatibility for what each tool consumes.
Quick map
AGENTS.md ← this file: registry + routing
CLAUDE.md ← project context (style, role, conventions)
.claude/
├── agents/ ← per-agent definitions + bundled assets
│ ├── product-manager/
│ │ ├── README.md
│ │ ├── sensors/ deterministic checks
│ │ ├── evals/ LLM-judge rubrics
│ │ ├── guides/ pipeline, writing style, templates, examples
│ │ └── skills/ prd, prp
│ ├── staff-software-engineer/
│ │ ├── README.md
│ │ ├── sensors/
│ │ ├── evals/
│ │ ├── guides/ pipeline, coding-style, commit-style, conventions-override
│ │ └── skills/ backend, web, mobile, devops, designer (new UIs)
│ ├── system-architect/
│ │ ├── README.md
│ │ ├── sensors/ design-structure, design-rigor
│ │ ├── evals/ design-quality, design-review-depth
│ │ ├── guides/ design-method (the canon), templates, example
│ │ └── skills/ design, review, search-engine (+ one per system design)
│ ├── product-manager.md orchestrator agent
│ ├── staff-software-engineer.md orchestrator agent
│ └── system-architect.md orchestrator agent
├── commands/ ← slash-command entry points
│ ├── golden-path.md /golden-path (front door: idea → merged PR)
│ ├── product-manager/ /product-manager:{prd,prp,run}
│ ├── sse/ /sse:{plan,dev,test,pr,run,sdd,firebase-publish}
│ ├── system-design/ /system-design:{design,review,run}
│ ├── context/ /context:{pack,graph}
│ └── pipeline/ /pipeline:{continue,reset}
├── shared/ ← cross-agent guides (context-strategy.md)
├── conventions/ ← generic conventions (overridable per repo)
├── hooks/ ← root lifecycle hooks (session-start, prompt, postedit, postwrite, status-line, activity-pre-read)
├── scripts/ ← root utilities (pipeline.py, activity.py, pr-monitor.py, marker.sh, preflight.sh, pack-repo.sh, graph-repo.sh)
└── runtime/ ← generated artifacts + per-agent hooks/scripts
├── outputs/
│ ├── pm/{prd,prp,tokens,.markers}/
│ └── sse/{plan,dev,test,pr,tokens,.markers}/
├── hooks/
│ ├── product-manager/ phase markers, sensor gates, eval, publish
│ └── staff-software-engineer/
└── scripts/
├── product-manager/ sensor-runner, token-phase, link-validator, confluence-publish, run-sensors.sh
└── staff-software-engineer/ token-phase, run-sensors.sh
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.
- 1mo ago First seen · 243 lines · 3,723 tokens per session scan C f688b302249f
harness-kit AGENTS.md is an instructions file published in the GitHub repository Pierry/harness-kit (4 stars, last pushed 12d ago), licensed MIT. It adds 3,723 tokens to every session, about $0.0149 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).