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/headroomlabs-ai/headroom/copilot-instructionsgit clone --depth 1 https://github.com/headroomlabs-ai/headroomWhat 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.00138 | $0.00138 |
| Opus 5 | $0.00069 | $0.00069 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
headroom 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 yesterday.
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
When performing a pull request review in this repository:
- Treat
.github/PULL_REQUEST_TEMPLATE.mdandCONTRIBUTING.mdas required policy, not optional guidance. - Flag pull requests that do not include concrete "Real Behavior Proof" with environment, exact commands or steps, observed result, and what was not tested.
- Be strict about contributor verification: missing tests, missing runtime evidence, or placeholder PR text should be called out.
- For user-facing, release, dependency, workflow, or security-sensitive changes, prefer blocking feedback over optional suggestions.
- Focus on correctness, safety, and whether the PR is actually ready for human maintainer review.
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.
- yesterday First seen · 8 lines · 138 tokens per session scan A ded6a77597b9
headroom copilot-instructions.md is an instructions file published in the GitHub repository headroomlabs-ai/headroom (68,175 stars, last pushed today), licensed Apache-2.0. It adds 138 tokens to every session, about $0.0007 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.
Other instructions, from other repositories
Acontext AGENTS.md
Instructions for memodb-io/Acontext, covering acontext, navigation guide, plan-driven development, modules and rules.
puppyone AGENTS.md
Instructions for puppyone-ai/puppyone, covering puppyone (contextbase), connect, collaborate, platform and active development directories.
framework AGENTS.md
Instructions for ai-driven-dev/framework, covering agents.md, behavior, communication, action and memory management.
puppyone CLAUDE.md
Instructions for puppyone-ai/puppyone: 项目文档和开发规范请参阅 AGENTS.md，此文件为唯一 source of truth。.
robrain AGENTS.md
Instructions for adelinamart/robrain, covering robrain — context management (oss self-hosted), session start (mandatory, first thing in every new chat), after every response (mandatory) and session end (last thing).
unigent AGENTS.md
Instructions for gintasz/unigent, covering setup — do this first in any fresh checkout or worktree, core vs. adapter, constitution, validation and releases.