Borrowing it
Nothing to install: this file belongs to bgauryy/octocode. 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/bgauryy/octocode/main/AGENTS.mdgit clone --depth 1 https://github.com/bgauryy/octocodeWrote 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/bgauryy/octocode/agents-md)<a href="https://agentmods.dev/instructions/bgauryy/octocode/agents-md"><img src="https://agentmods.dev/badge/instructions/bgauryy/octocode/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.03138 | $0.03138 |
| Opus 5 | $0.01569 | $0.01569 |
| Sonnet 5 | $0.00628 | $0.00628 |
| Haiku 4.5 | $0.00314 | $0.00314 |
Grade A, and why
octocode 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 6d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Octocode Monorepo
Default agent guide for this repo. Internals: each package’s ARCHITECTURE.md when present.
Dogfood
This monorepo is the platform. Use what we ship — do not reinvent with host defaults.
| Need | Use | Not |
|---|---|---|
| Local code search / structure / files / content / LSP | Octocode MCP or node packages/octocode/out/octocode.js tools … — all local tools below |
bare find / grep / rg / cat / ls |
| GitHub code, repos, PRs/commits, clone | same — all GitHub tools below | ad-hoc gh / raw API (except when Octocode is unavailable) |
| npm lookup | npmSearch |
ad-hoc registry curls |
| Unified research | raw tools <name> invocation (CLI or MCP) |
hand-rolled multi-tool scripts |
| Research / review / change flows | octocode-research skill |
inventing search loops |
| Measure “did this help?” / keep-discard | octocode-graph-eval skill |
vibe acceptance / editing graders to pass |
| Offload low-risk bulk to local Ollama | octocode-subagent (references/local-ollama.md) |
cloud-only token burn / inventing Ollama loops |
| After a package change | rebuild → real CLI / MCP / skill path | claim done from compile alone |
If dogfooding hurts, fix or record it — do not silently bypass.
Method: Plan → TDD → yarn workspace <pkg> test → yarn lint → verify. No backward compat by default — refactor freely; add shims only when asked.
Access: packages/*/src/, tests/, docs/ ✅ · *.json, *.config.*, Cargo.toml, scripts/ ⚠️ ask · .env*, node_modules/, dist/, out/, target/ ❌
Architecture
INTERFACES octocode-mcp (stdio MCP) octocode (CLI) octocode-vscode (VS Code)
└─────────────────────┴── depend on ──┐
BRAIN @octocodeai/octocode-tools-core (all tool execution logic)
├── metadata ──▶ @octocodeai/octocode-core (external: schemas, descriptions, system prompt)
├── native ──▶ @octocodeai/octocode-engine (Rust/napi: search, minify, LSP, secrets)
└── config ──▶ @octocodeai/config (env/config loader — zero-dep, single source)
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.
- 6d ago First seen · 163 lines · 3,138 tokens per session scan A 839447f66c23
octocode AGENTS.md is an instructions file published in the GitHub repository bgauryy/octocode (924 stars, last pushed 2d ago), licensed MIT. It adds 3,138 tokens to every session, about $0.0157 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
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.