Borrowing it
Nothing to install: this file belongs to orangeboyChen/codebuddy2api. 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/orangeboyChen/codebuddy2api/main/AGENTS.mdgit clone --depth 1 https://github.com/orangeboyChen/codebuddy2apiWrote 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/orangeboychen/codebuddy2api/agents-md)<a href="https://agentmods.dev/instructions/orangeboychen/codebuddy2api/agents-md"><img src="https://agentmods.dev/badge/instructions/orangeboychen/codebuddy2api/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/orangeboychen/codebuddy2api/agents-md"><img src="https://agentmods.dev/badge/instructions/orangeboychen/codebuddy2api/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.00779 | $0.00779 |
| Opus 5.5 | $0.00312 | $0.00312 |
| Sonnet 5.5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade A, and why
codebuddy2api 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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Commit Rules
- Use English conventional commits, for example
feat: reorganize source layout. - Do not commit until
bun run lint,bun run format:check,bun run typecheck,bun run test:coverage, andbun run buildall pass. - Unit test coverage must stay at or above the enforced thresholds; see Coverage Thresholds. Do not commit code below them.
Code Style
- Write comments in English only.
- Keep README, deployment manifests, GitHub Actions, and Dependabot aligned with the current repository structure.
- Prefer Bun for dependency management and local commands.
- Prefer TypeScript for application and test code whenever a new file or rewrite is needed.
- Use arrow functions only. Do not introduce
functiondeclarations; preferconst name = () => {}consistently. - Do not leave unused variables in committed code. Remove them or rename intentionally ignored values with a leading underscore only when the linter rule allows it.
- When changing user-visible copy, review every supported locale in
messages/and keep equivalent wording aligned across them.
Verification Before Commit
- Run
bun run lint. - Run
bun run format:check. - Run
bun run typecheck. - Treat unit test coverage below the enforced thresholds as a blocking failure.
- Run
bun run test:coverageand confirm lines, statements, and functions are at or above 90% and branches at or above 70%. - Run
bun run build.
Verification Before PR
- Run
bun run test:cito generatecoverage/lcov.infoandtest-report.junit.xml. - Run
bun run test:patch-branches --base "$(git merge-base HEAD origin/main)"after coverage; changed branch coverage must be at least 90%. - Confirm Codecov's
patchstatus is successful and meets the target configured incodecov.yml; do not lower the patch target or threshold to bypass a coverage failure. - Use the Codecov PR report as the source of truth for patch coverage because it compares the uploaded
lcov.infoagainst the PR base commit.
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 Changed · +16 lines · +200 tokens per session 96594abbcd65
- 1mo ago Changed · -1 lines · -28 tokens per session 546b1580af95
- 1mo ago First seen · 45 lines · 607 tokens per session scan A fc414f06ee78
codebuddy2api AGENTS.md is an instructions file published in the GitHub repository orangeboyChen/codebuddy2api (33 stars, last pushed yesterday), licensed MIT. It adds 779 tokens to every session, about $0.0031 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-30.
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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.