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/orangeboychen/codebuddy2api/agents-mdgit clone --depth 1 https://github.com/orangeboyChen/codebuddy2apiWhat 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.00607 | $0.00607 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 45 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. - Use the Codex identity for Codex-authored commits:
codex <[email protected]>. - 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 90%; do not commit code below the enforced coverage threshold.
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 90% as a blocking failure.
- Run
bun run test:coverageand confirm the reported coverage stays at or above 90%. - 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.
- yesterday 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 (11 stars, last pushed yesterday), licensed MIT. It adds 607 tokens to every session, about $0.0030 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-30.
Other instructions, from other repositories
recharts AGENTS.md
Instructions for recharts/recharts: This is Recharts repository. Recharts is a React-based charting library. The goal is to provide a simple, declarative, and composable way to build charts. We value consistency, usability, and performance. Accessibility is important.
openscreen AGENTS.md
Instructions for getopenscreen/openscreen, covering agents.md, setup commands, development principles, project layout and code style.
spec-kit-zh AGENTS.md
Instructions for loulanyue/spec-kit-zh, covering agents.md, about spec kit and specify, general practices, adding new agent support and current supported agents.
GameDesignOS AGENTS.md
Instructions for DY-2026/GameDesignOS, covering gamedesignos agent 入口, 默认接法, agent 执行规则, 什么时候用整个项目 and 每个 skill 单独怎么用.
open-dictionary AGENTS.md
Instructions for ahpxex/open-dictionary, covering open dictionary rewrite charter, product framing, core workflow, technical framework and 1. raw ingestion layer.
skill-buddy AGENTS.md
Instructions for konnga/skill-buddy, a project described as: AI Skills Buddy, A desktop workspace for managing, installing, and synchronizing Skills and MCP Servers across AI agents.