rebar AGENTS.md

Repository instructions for agents working on rebar, including required documents to read, collaboration rules, project contracts, and session practices.

In plain words
What is it for?
Use them at the start of a rebar coding session to orient the agent and guide planning, collaboration, debugging, and implementation.
Why use it?
They give an agent the project’s current context and operating agreements before it changes code, reducing the risk of ignoring local expectations or breaking established contracts.

Instructions file for CodexOpenCode

Install

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.

agentmods
npx agentmods add instructions/willackerly/rebar/agents-md
Clone the repo
git clone --depth 1 https://github.com/willackerly/rebar

Made for: Codex, OpenCode.

Per session 1,577 This file is loaded in full into every session.
When invoked 1,577 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01577 $0.01577
Opus 5 $0.00788 $0.00788
Sonnet 5 $0.00315 $0.00315
Haiku 4.5 $0.00158 $0.00158

Measured yesterday against content hash 13847bae37ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

rebar 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 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.

AGENTS.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md — working on rebar itself

rebar v3.0.0-beta.2 | Tier 3: ENFORCED — this repo dogfoods its own methodology.

Read Before Coding

Cold Start Quad (every session, every agent, no exceptions):

  1. README.md — universal orientation
  2. QUICKCONTEXT.md — current state (verify against git log --oneline -10)
  3. TODO.md — task list + pointer to INVENTORY.md (canonical planning surface)
  4. AGENTS.md (this file) — norms, contracts, collaboration

Then, before your first substantive action: 5. .claude-memory-commits/working-agreements/ — how this maintainer wants an agent to operate here. Six short files; read all of them. They are the collaboration contract, not architecture, and they are checked in precisely so they survive a machine move, a tool change, or a different agent.

Reference:

  • DESIGN.md — the philosophy (contracts are the operating system)
  • .claude-memory-commits/environment/ — MCP/ASK debugging gotchas, indexed by symptom
  • architecture/CONTRACT-REGISTRY.md — contract index
  • architecture/CONTRACT-*.md — current contracts (S1-STEWARD, S2-ASK-CLI, S3-MCP-SERVER)
  • practices/ — orchestration, session lifecycle, red team, fidelity, e2e
  • feedback/INVENTORY.md — vote-shaped accumulator + Maintainer Queue

Core Tenets

  1. Eat your own dog food. Every change to rebar's methodology must hold up when applied to the rebar repo itself. If the cookie-cutter template would produce a structure rebar doesn't follow, fix the template AND rebar.
  2. Mechanical over manual. When you find yourself doing the same drift fix by hand, ship a script that catches it next time (check-doc-refs.sh, check-decay-patterns.sh, sync-bootstrap.sh are recent examples).
  3. One canonical planning surface. feedback/INVENTORY.md is the index. Don't recreate parallel planning docs at root — append to INVENTORY.

Agent Autonomy

Maximum autonomy granted. Act decisively. Ship code. Don't ask permission for routine work.

Read the full file on GitHub · 133 lines

Changes

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.

  1. yesterday First seen · 133 lines · 1,577 tokens per session scan A 13847bae37ea

Subscribe to this mod's changes

rebar AGENTS.md is an instructions file published in the GitHub repository willackerly/rebar (5 stars, last pushed 19d ago), licensed Apache-2.0. It adds 1,577 tokens to every session, about $0.0079 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.