codebuddy2api AGENTS.md

Repository rules for the codebuddy2api project, covering coding style, commits, translations, and required checks before changes are committed or proposed.

In plain words
What is it for?
Use it when editing codebuddy2api, especially for TypeScript or Bun work, commits, tests, formatting, builds, and pull requests.
Why use it?
It gives an agent the project’s working rules so changes follow the repository’s standards and are checked before review.

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/orangeboychen/codebuddy2api/agents-md
Clone the repo
git clone --depth 1 https://github.com/orangeboyChen/codebuddy2api

Made for: Codex, OpenCode.

Per session 607 This file is loaded in full into every session.
When invoked 607 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.00607 $0.00607
Opus 5 $0.00303 $0.00303
Sonnet 5 $0.00121 $0.00121
Haiku 4.5 $0.00061 $0.00061

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

Security

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.

AGENTS.md · 45 lines

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, and bun run build all 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 function declarations; prefer const 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:coverage and confirm the reported coverage stays at or above 90%.
  • Run bun run build.

Verification Before PR

  • Run bun run test:ci to generate coverage/lcov.info and test-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 patch status is successful and meets the target configured in codecov.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.info against the PR base commit.

Read the full file on GitHub · 45 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 · 45 lines · 607 tokens per session scan A fc414f06ee78

Subscribe to this mod's changes

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.