Borrowing it
Nothing to install: this file belongs to xiaojiou176-open/BrewMe. 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/xiaojiou176-open/BrewMe/main/AGENTS.mdgit clone --depth 1 https://github.com/xiaojiou176-open/BrewMeWrote 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/xiaojiou176-open/brewme/agents-md)<a href="https://agentmods.dev/instructions/xiaojiou176-open/brewme/agents-md"><img src="https://agentmods.dev/badge/instructions/xiaojiou176-open/brewme/agents-md.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.1 | $0.01245 | $0.01245 |
| Opus 5 | $0.00622 | $0.00622 |
| Sonnet 5 | $0.00249 | $0.00249 |
| Haiku 4.5 | $0.00125 | $0.00125 |
Grade A, and why
BrewMe 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Collaboration Contract
This repository is a public, source-first engineering project. The public surface MUST stay thin, truthful, and easy to navigate.
Core Rules
README.mdis the front door.docs/start-here.mdis the quickstart and operator entrypoint.docs/architecture.mdis the system map.docs/testing.mdis the testing and CI contract.- Runtime, cache, logs, and agent workspaces MUST stay out of the tracked public surface.
- Root documentation MUST stay concise and public-facing. Internal audit logs, rehearsal notes, and execution ledgers MUST NOT return.
- AI agents MUST read before editing, prefer surgical changes, and verify meaningful behavior with real commands.
- Commits, branch rewrites, and force-pushes are allowed only when explicitly authorized by the human maintainer.
- Browser automation MUST stay repo-scoped, state-aware, and cleanup-first: do not accumulate extra Chrome/Chromium/Safari instances, cloned profiles, or large tab sets, and do not borrow browser state opened by other repos or other L1s on the same machine.
- Docker and runtime residue MUST stay governed: do not leave disposable containers, caches, or duplicate runtime workspaces behind after verification when they are no longer needed.
- External-account writes stay opt-in only: never change GitHub profile settings, browser-signed-in account state, Resend/Google account settings, or other third-party account data unless the human maintainer explicitly authorizes that exact write.
- Login-state probing MUST stay bounded: if the repo-scoped real browser profile is still not logged in after one or two focused checks, record a blocker and stop escalating browser churn.
- Browser focus and machine-wide resource contention MUST be respected: avoid stealing desktop focus when possible, and if the machine already has more than six browser instances open, wait for other repo workflows to release resources before opening another one.
- Current-cycle branch, worktree, and PR residue MUST be closed out before declaring completion: merge active work into
main, or evidence-close and delete branches that are already fully absorbed. - Release truth and current-
maintruth MUST be stated separately and honestly: if the latest release lags currentmain, document that gap explicitly instead of implying they are the same snapshot.
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.
- 8d ago First seen · 78 lines · 1,245 tokens per session scan A 0efabe95ae67
BrewMe AGENTS.md is an instructions file published in the GitHub repository xiaojiou176-open/BrewMe (2 stars, last pushed 3mo ago), licensed MIT. It adds 1,245 tokens to every session, about $0.0062 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).
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).
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.
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.