Borrowing it
Nothing to install: this file belongs to andr-ca/agentharness. 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/andr-ca/agentharness/main/AGENTS.mdgit clone --depth 1 https://github.com/andr-ca/agentharnessWrote 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/andr-ca/agentharness/agents-md)<a href="https://agentmods.dev/instructions/andr-ca/agentharness/agents-md"><img src="https://agentmods.dev/badge/instructions/andr-ca/agentharness/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.1 | $0.07494 | $0.07494 |
| Opus 5 | $0.03747 | $0.03747 |
| Sonnet 5 | $0.01499 | $0.01499 |
| Haiku 4.5 | $0.00749 | $0.00749 |
Grade A, and why
agentharness 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 2d 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.
This is a copy
98% identical to agentharness copilot-instructions.md — 31 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 432 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Generated from this repo's own CLAUDE.md by tools/generate-agents-md.sh
(https://github.com/andr-ca/agentharness) — do not hand-edit; regenerate instead
(tools/generate-agents-md.sh --output AGENTS.md). A CI check keeps this
file in sync with its source (see .github/workflows/ci.yml's
content-quality job).
This file covers repo-wide routing rules only. Skills are loaded on
demand from .agents/skills/ — Codex CLI's real skill mechanism (the
Agent Skills open standard, shared with Claude Code) scans that
directory from the working directory up to the repo root, reads each
SKILL.md's name/description metadata up front, and loads a skill's
full body only once its description matches the task at hand. The index
below exists so that metadata-scan step has something to match against;
it is not a substitute for reading the matched SKILL.md itself.
agentharness – Agent Router
This file is loaded into every session that touches this repo. Keep it short — everything else is one link away. Full index: MANIFEST.md. Planned-but-not-built: ROADMAP.md.
🤖 Agent Workflow Completion
Default (no publish authority): verify and stage, then stop.
- ✅ Run the completion gate — before declaring any work done, run
bash tools/check-completion.sh. This script verifies lint, types, tests, coverage, and content quality in one shot and exits non-zero if anything fails. The Stop hook in.github/hooks/completion-gate.jsonand.claude/settings.jsonenforces this automatically for Claude Code and GitHub Copilot — the agent cannot stop until all gates pass. - ✅ Create atomic commits locally — one logical unit per commit, clear message explaining WHY
- 🛑 Stop before pushing, opening a PR, or auto-implementing recommendations. Present a summary of what's staged and ask the user to confirm before publishing anything.
A local commit is not a durable safe-point in an ephemeral-container
execution environment. If you have verified, committed-but-unpushed
work and are about to block on AskUserQuestion or other unbounded
human input, consider pushing to a remote branch (a scratch/WIP branch
is fine) first — committed-but-unpushed work can be lost if the
container is reclaimed during the wait, with no error at commit time
and no warning until a later git log looks unfamiliar. This is
disclosure of an existing risk, not a grant of publish authority: it
does not authorize opening a PR or merging, and the default tier above
still governs those.
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.
- 2d ago First seen · 432 lines · 7,494 tokens per session scan A 95892cd73b0d
agentharness AGENTS.md is an instructions file published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 3d ago), licensed MIT. It adds 7,494 tokens to every session, about $0.0375 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to agentharness copilot-instructions.md, differing in 31 lines, and is treated as a copy.
Other instructions, from other repositories
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.
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.
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).
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).
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.
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.