Borrowing it
Nothing to install: this file belongs to JJHbrams/Project-AMBER. 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/JJHbrams/Project-AMBER/master/AGENTS.mdgit clone --depth 1 https://github.com/JJHbrams/Project-AMBERWrote 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/jjhbrams/project-amber/agents-md)<a href="https://agentmods.dev/instructions/jjhbrams/project-amber/agents-md"><img src="https://agentmods.dev/badge/instructions/jjhbrams/project-amber/agents-md/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/jjhbrams/project-amber/agents-md"><img src="https://agentmods.dev/badge/instructions/jjhbrams/project-amber/agents-md.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.00400 | $0.00400 |
| Opus 5.5 | $0.00160 | $0.00160 |
| Sonnet 5.5 | $0.00080 | $0.00080 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
Project-AMBER 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 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.
What it actually says
Agent orchestration
The root session is the Orchestrator. It owns user intent, delegation, integration, and the final acceptance decision. Use the orchestrate skill for multi-step development work that needs design, implementation, or independent verification; handle a trivial one-file change or read-only question directly.
Roles
| Role | Runtime mapping | Responsibility |
|---|---|---|
| Orchestrator | root session (Sol, high) | intent, routing, integration, acceptance gates |
| Planner | planner (Terra, medium) |
read-only plan and fresh acceptance audit |
| Coder | coder (Terra, medium) |
bounded implementation and criterion evidence |
| Servant | servant (Luna, low) |
bounded discovery, commands, and mechanical work |
These are behavioral roles. Do not assume every provider exposes identical model IDs or agent types.
Non-negotiable rules
- Turn the original request into an acceptance contract before implementation. Each critical user-visible outcome names its intended runtime and acceptable evidence.
- Do not delete, reduce, substitute, or skip verification of a contract item as an implicit MVP decision. Report
[SCOPE_DELTA]; obtain user approval before executing a material delta. - After implementation, request a fresh
planneracceptance audit. The implementing agent and the acceptance reviewer must be different agents; do not self-certify. - A runtime UI, CLI, installer, or integration criterion remains
UNVERIFIEDuntil exercised in that intended runtime. Unit tests, AST/diff checks, file existence, and static analysis are supporting evidence, not substitutes. - Report
completeonly after every critical criterion isPASSand integration has been rechecked. Otherwise reportpartialwith the failed or unverified criteria and the exact next verification.
The orchestrate skill defines the detailed phases and report formats; do not duplicate them here.
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 First seen · 25 lines · 400 tokens per session scan A 6b81bd286fa3
Project-AMBER AGENTS.md is an instructions file published in the GitHub repository JJHbrams/Project-AMBER (2 stars, last pushed 24d ago), licensed MIT. It adds 400 tokens to every session, about $0.0016 per session on Opus 5.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
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.