Borrowing it
Nothing to install: this file belongs to awizemann/harness. 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/awizemann/harness/main/.github/copilot-instructions.mdgit clone --depth 1 https://github.com/awizemann/harnessWrote 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/awizemann/harness/copilot-instructions)<a href="https://agentmods.dev/instructions/awizemann/harness/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/awizemann/harness/copilot-instructions/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/awizemann/harness/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/awizemann/harness/copilot-instructions.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.00571 | $0.00571 |
| Opus 5.5 | $0.00228 | $0.00228 |
| Sonnet 5.5 | $0.00114 | $0.00114 |
| Haiku 4.5 | $0.00057 | $0.00057 |
Grade A, and why
harness copilot-instructions.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 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.
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
100% identical to scarf copilot-instructions.md — 0 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.
What it actually says
Memory System (managed by Memophant) — core rules. Full reference: AGENTS.md.
- Memory is the source of truth. Search it before assuming; record durable decisions/learnings as memory notes or wiki pages — never in this file or session-private/model memory. Search before writing and edit an existing note (
edit_memory) rather than forking a near-duplicate. - Prefer the
memophantMCP tools for every read/write (search/read/write/edit/move) — read each tool's description (they document their args). The engine is the gate: the tool/app entry points carry the guards (slug-gen, structure validation, write-time secret scan); direct edits reconcile automatically but skip them — never compose your own guard set. Tools absent → grep the MAIN CHECKOUT's.memory/+wiki/; a git worktree's copy of those tiers is a base-commit snapshot and is stale by construction, so never grep./from one. - Don't
git add/committhe managed tiers (.memory/,wiki/,design/,code/,sessions/,documents/,vendors/,templates/,TASKS.md,tasks/) — the user commits each via Memophant's per-tier secret-scanned bar; leave them dirty. Everything else is yours. - Secrets → Keychain, never chat or files. Found or made a credential? Store it with
set_vendor_credential(fetch later withget_vendor_credential); never leave it loose in chat. - Agent artifacts (plans/reports/briefs) →
documents/(exact lowercase), viawrite_tier_file(tier: "documents", path: …)— never a repo'sdocs/folder (that's the project's own documentation) and never a case-variant likeDocuments/. - Read the project charter (
read_charter) at session start when this project has one (.memory/charter.md) — its commandments are absolute and OUTRANK memory notes, this file, and your brief; "No charter" is a normal answer. It's human-only: propose changes as a task taggedcharter, never edit it. File memory notes under one of six folders (architecture/conventions/decisions/operations/project/roadmap), never the root. When a note is grounded in code, passsource_paths(the repo files it depends on) so Memory Health can drift-check it — an unanchored code note can't be kept current.
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 Changed · +1 lines · +110 tokens per session f4e6c75d54f7
- 1mo ago First seen · 11 lines · 461 tokens per session scan A ddf71ea4538e
harness copilot-instructions.md is an instructions file published in the GitHub repository awizemann/harness (357 stars, last pushed 1mo ago), licensed MIT. It adds 571 tokens to every session, about $0.0023 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to scarf copilot-instructions.md, differing in 0 lines, and is treated as a copy.
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.
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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.