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/gemyago/atlacp/agents-mdgit clone --depth 1 https://github.com/gemyago/atlacpWrote 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/gemyago/atlacp/agents-md)<a href="https://agentmods.dev/instructions/gemyago/atlacp/agents-md"><img src="https://agentmods.dev/badge/instructions/gemyago/atlacp/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 | $0.01616 | $0.01616 |
| Opus 5 | $0.00808 | $0.00808 |
| Sonnet 5 | $0.00323 | $0.00323 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
atlacp 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 4d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
This is a golang backend project with OpenTelemetry integration for observability. Go version is defined in go.mod file and this is the primary source of truth for the version.
Purpose & Precedence
- This file gives AI coding agents the exact commands and conventions to follow in this repo.
- Closest AGENTS.md to the edited file applies; walk up directories to root if none found.
- Treat this as living documentation: update it in the same PR as any build/test/arch changes.
- ALWAYS follow "Task Completion Protocol" prior to reporting task completion
Quick Setup
- direnv is assumed to be already configured.
- In this environment, commands do not automatically source
.envrc; run with:direnv allow .direnv exec . go test ./...(or any other command)
- gobrew is used to manage Go versions
- Install deps/tools:
go mod download && go install tool - Lint:
make lint - Run tests:
make test
Test and Lint
- Run all tests:
make test - Lint entire codebase:
make lint - Run a specific test:
go test -v ./internal/... -run "^TestName$" - Attempt auto fixing linting issues:
bin/golangci-lint run --fix
Run (local)
AI must always use --noop flag to dry-run startup checks without external deps. Without this flag, processes will start in foreground and block.
- MCP server (stdio):
go run ./cmd/bbcp stdio --env local --noop - MCP server (HTTP):
go run ./cmd/bbcp http --env local --noop - Bitbucket CLI (
bbmd):go run ./cmd/bbmd --help bbmdlist accounts (JSON):go run ./cmd/bbmd auth statusbbmdread PR (JSON):go run ./cmd/bbmd pr read --repo-owner <owner> --repo-name <repo> --pr-id <id>
--noop on bbmd wires dependencies and skips real Bitbucket/account calls (dry-run / startup checks).
Docker Images (multi-platform)
- Build local images (load):
make -C build docker/.local-images - Build & push remote images:
make -C build docker/.remote-images - Configure platforms/registries in:
build/build.cfg
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.
- 4d ago First seen · 138 lines · 1,616 tokens per session scan A 90a65ee11845
atlacp AGENTS.md is an instructions file published in the GitHub repository gemyago/atlacp (7 stars, last pushed 4mo ago), licensed MIT. It adds 1,616 tokens to every session, about $0.0081 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
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.
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.