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/betta-tech/byo-coding-agent/agents-mdgit clone --depth 1 https://github.com/betta-tech/byo-coding-agentWhat 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.00647 | $0.00647 |
| Opus 5 | $0.00324 | $0.00324 |
| Sonnet 5 | $0.00129 | $0.00129 |
| Haiku 4.5 | $0.00065 | $0.00065 |
Grade A, and why
byo-coding-agent 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 2d 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.
Project context for AI agents
This file is loaded into the system prompt at startup by the harness itself
(see loadAgentsContext in main.go) and is also picked up by external
agents like Claude Code that follow the AGENTS.md convention.
What this repo is
A small, opinionated coding-agent harness in Go (~1,000 lines), written as a
learning project. The README and follow_along/ chapters explain why each
piece exists.
Layout
main.go— wiring: provider, tools, MCP servers, AGENTS.md, root agent, TUI.commands.go— slash command registry. Touches every extension point.delegate.go— the delegate tool. Lives in main to avoid an import cycle.internal/api/— shared message types. No internal deps.internal/provider/—Providerinterface + Anthropic adapter.internal/tool/—Toolinterface,Registry, one file per local tool.internal/mcp/— wrappers that expose remote MCP server tools as local Tools.internal/compact/— compaction strategies (no-op, sliding window, summarize, logging decorator).internal/agent/— the agent loop. OneAgentper conversation.internal/subagent/—Subagentinterface + research subagent + active tracker.internal/ui/— banner, spinner, the Bubble Tea program that owns the UI.
Conventions
- Errors as tool results, not Go errors. When a tool fails, return
(message, true)so the model can read and recover. Don't crash the loop. - One file per tool / strategy / subagent. Tools self-register via
init(); subagents register explicitly inmainbecause they need aProviderat construction time. - The provider abstraction is real. Anthropic SDK types are only allowed
in
internal/provider/anthropic.go. If you find them anywhere else, that's a leak. - Comments explain why, not what. Names carry the what.
Build / run
export ANTHROPIC_API_KEY=sk-ant-...
go run . # launches the TUI
go build ./... # sanity check
go vet ./... # before committing
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.
- 2d ago First seen · 60 lines · 647 tokens per session scan A 6a06f0cde861
byo-coding-agent AGENTS.md is an instructions file published in the GitHub repository betta-tech/byo-coding-agent (140 stars, last pushed 3mo ago), licensed MIT. It adds 647 tokens to every session, about $0.0032 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
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 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).
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.