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/navapbc/rebar/copilot-instructionsgit clone --depth 1 https://github.com/navapbc/rebarWrote 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/navapbc/rebar/copilot-instructions)<a href="https://agentmods.dev/instructions/navapbc/rebar/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/navapbc/rebar/copilot-instructions.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.00397 | $0.00397 |
| Opus 5 | $0.00198 | $0.00198 |
| Sonnet 5 | $0.00079 | $0.00079 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
rebar 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 5d 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
rebar — GitHub Copilot entry point
The canonical agent & contributor guidance for this repo lives in AGENTS.md at the
repository root. GitHub Copilot's coding agent already reads AGENTS.md natively, exactly as
Codex does (see AGENTS.md's own note on this); this file exists so that other Copilot
surfaces — Copilot Chat and the Copilot CLI running in this checkout — are pointed at that same
canonical source instead of drifting from it, mirroring the bridge CLAUDE.md provides for
Claude Code via its @AGENTS.md import.
Read and follow AGENTS.md in full before doing any work in this repository. It covers,
among other things:
-
Recording work in rebar tickets (not scratch notes), and claiming a ticket before touching code.
-
The parallel-agent ticket workflow (
list/search→ready/next-batch→claim→ work →transition closed). -
The module-size policy and code-navigation tooling (Serena vs.
grep) for editing rebar itself. -
The Gerrit-based git workflow for landing changes —
mainis not merged via GitHub PRs; changes go throughgit push gerrit HEAD:refs/for/mainand requireLLM-Review +1andVerified +1before Submit. -
Pointers into
docs/for ticket model, gate protocols, MCP tools, concurrency, and more. -
Put anything all harnesses need in
AGENTS.md, not here. -
Keep any genuinely Copilot-specific instructions in this file, below this note.
-
Do not duplicate
AGENTS.mdcontent here beyond this summary — if the two ever diverge,AGENTS.mdis authoritative.
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.
- 5d ago First seen · 28 lines · 397 tokens per session scan A 11e079ce2265
rebar copilot-instructions.md is an instructions file published in the GitHub repository navapbc/rebar (4 stars, last pushed today), licensed Apache-2.0. It adds 397 tokens to every session, about $0.0020 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
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).
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.
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).