Borrowing it
Nothing to install: this file belongs to ludan12138/buddy-companion. 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/ludan12138/buddy-companion/main/AGENTS.mdgit clone --depth 1 https://github.com/ludan12138/buddy-companionWrote 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/ludan12138/buddy-companion/agents-md)<a href="https://agentmods.dev/instructions/ludan12138/buddy-companion/agents-md"><img src="https://agentmods.dev/badge/instructions/ludan12138/buddy-companion/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/ludan12138/buddy-companion/agents-md"><img src="https://agentmods.dev/badge/instructions/ludan12138/buddy-companion/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.00533 | $0.00533 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
buddy-companion 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 10d 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 — 24 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
SKILL.md is the runtime entrypoint and the main source of truth for companion behavior. README.md and README.zh.md document installation, usage, and the persistence contract. Reference data lives in references/ (sprites.md for ASCII art, personalities.md for naming and tone). Design notes and change planning live under docs/superpowers/specs/ and docs/superpowers/plans/. Automated checks currently live in tests/, with tests/skill-growth-contract.sh validating required growth-related documentation.
Build, Test, and Development Commands
There is no build step for this repository; changes are mostly Markdown and shell-based validation.
sh tests/skill-growth-contract.sh: verifies thatSKILL.mdandREADME.mdstill include required growth-system terms.git diff --check: catches whitespace errors before opening a PR.rg "pattern" .: preferred way to find command names, persisted keys, or wording across docs.
Coding Style & Naming Conventions
Keep edits Markdown-first, concise, and implementation-facing. Use ATX headings (## Heading), short paragraphs, and fenced blocks for examples. Preserve persisted field names exactly as lower_snake_case, for example hatchedAt, streak_days, and last_active_on, to avoid breaking documented contracts. Shell scripts should stay POSIX sh unless the repo explicitly adopts Bash-only features.
Testing Guidelines
Run sh tests/skill-growth-contract.sh after any change to SKILL.md, README.md, or persistence/growth language. When behavior changes, update the contract test in the same change so documentation and validation stay aligned. Name new test scripts descriptively, following the current pattern of hyphenated shell filenames in tests/.
Commit & Pull Request Guidelines
Recent history favors short, imperative subjects, often with a conventional prefix such as docs: or feat:. Follow that style when possible, for example docs: clarify persistence fallback or feat: expand buddy mood rules. PRs should include a brief summary, the reason for the change, and the exact checks run. If output visible to users changes, include a small terminal example or README snippet showing the new behavior.
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.
- 10d ago First seen · 24 lines · 533 tokens per session scan A 649582301338
buddy-companion AGENTS.md is an instructions file published in the GitHub repository ludan12138/buddy-companion (5 stars, last pushed 5mo ago), licensed MIT. It adds 533 tokens to every session, about $0.0027 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).
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.
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.