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/motosan-dev/acp-cli/agents-mdgit clone --depth 1 https://github.com/motosan-dev/acp-cliWhat 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.01147 | $0.01147 |
| Opus 5 | $0.00574 | $0.00574 |
| Sonnet 5 | $0.00229 | $0.00229 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
acp-cli 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — acp-cli Development Brief
Read this before writing any code.
Project Overview
acp-cli is a headless CLI client for the Agent Client Protocol (ACP). It spawns coding agents (Claude, Codex, Gemini, etc.) as child processes and communicates over structured JSON-RPC via stdio pipes.
- Version: 0.2.1
- Language: Rust (edition 2024)
- Published to: crates.io (
acp-cli) - GitHub: https://github.com/motosan-dev/acp-cli
Repository Structure
acp-cli/
├── Cargo.toml
├── src/
│ ├── main.rs # CLI entry point
│ ├── lib.rs # Library re-exports
│ ├── config.rs # Config loading + merging
│ ├── error.rs # Error types (thiserror)
│ ├── agent/registry.rs # Agent name → command mapping
│ ├── bridge/ # AcpBridge (spawn_blocking + LocalSet)
│ ├── cli/ # Commands: init, prompt, exec, sessions
│ ├── client/ # BridgedAcpClient + permission resolution
│ ├── output/ # Renderers: text, json, quiet
│ ├── queue/ # Queue owner/client, IPC, lease
│ └── session/ # Session scoping, persistence, history
├── skills/acp-cli/ # AI skill card
├── README.md
├── llms.txt # LLM-consumable API reference
├── CLAUDE.md # Claude Code project instructions
├── CHANGELOG.md
└── LICENSE
Key Design Decisions
- !Send bridge pattern — ACP SDK uses
Rc/spawn_local; bridge runs inspawn_blocking+LocalSet, communicates via mpsc channels - Queue system — first process becomes queue owner (holds agent connection), subsequent processes connect as clients via Unix socket
- Session scoping — key is
SHA-256(agent + "\0" + git_root + "\0" + name), ensuring isolation per project/agent/name - Auth token chain — env var → config file →
~/.claude.json→ macOS Keychain (never guess, always explicit) - Permission modes — three modes (approve-all, approve-reads, deny-all) applied at BridgedAcpClient level
- Agent registry — hardcoded defaults + config overrides + raw command fallback
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 · 134 lines · 1,147 tokens per session scan A ed4c88d50361
acp-cli AGENTS.md is an instructions file published in the GitHub repository motosan-dev/acp-cli (11 stars, last pushed 5mo ago), licensed MIT. It adds 1,147 tokens to every session, about $0.0057 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
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.