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/normahq/codex-acp-bridge/agents-mdgit clone --depth 1 https://github.com/normahq/codex-acp-bridgeWrote 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/normahq/codex-acp-bridge/agents-md)<a href="https://agentmods.dev/instructions/normahq/codex-acp-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/normahq/codex-acp-bridge/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.00743 | $0.00743 |
| Opus 5 | $0.00371 | $0.00371 |
| Sonnet 5 | $0.00149 | $0.00149 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
codex-acp-bridge 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
codex-acp-bridge — AGENTS.md
Development Standards
- Follow idiomatic Go and Google Go best practices.
- Prefer project-local tooling via
go tool ...when available. - Use Conventional Commits for all commits.
- Sync shared branches with merge (
git pull --no-rebase), not rebase.
Quality Gates (Required)
Run before submitting changes:
go test -race ./...
go tool golangci-lint run
Logging Policy
- Allowed:
github.com/rs/zerolog,log/slog. - Disallowed:
logrus,zap, direct standardlogusage. - Initialize logging through
internal/logging.Init(). - Prefer structured logging fields over formatted strings.
Bridge Guardrails
- Keep ACP contract compatibility stable.
- Keep strict validation for
session/new._meta.codex. - Keep model handling ACP-native (
session/set_config_optionwith config IDmodel), keep legacysession/set_modelcompatibility, and do not add bridge-specific model CLI flags. - Keep MCP transport constraints aligned with implementation (
stdioandhttp, rejectsse).
Documentation
- Product/usage docs are rooted in
README.md. - Protocol details are in:
docs/usage.mddocs/json-api.md
Release
- Omnidist profile is authoritative (
.omnidist/omnidist.yaml). - Version source is Git tags (
version.source: git-tag). - Publish flow is tag-driven via GitHub Actions release workflow.
Beads Issue Tracker
This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.
Quick Reference
bd ready # Find available work
bd show <id> # View issue details
bd update <id> --claim # Claim work
bd close <id> # Complete work
Rules
- Use
bdfor ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists - Run
bd primefor detailed command reference and session close protocol - Use
bd rememberfor persistent knowledge — do NOT use MEMORY.md files
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 · 92 lines · 743 tokens per session scan A cbad56ecdad2
codex-acp-bridge AGENTS.md is an instructions file published in the GitHub repository normahq/codex-acp-bridge (3 stars, last pushed 9d ago), licensed MIT. It adds 743 tokens to every session, about $0.0037 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
deer-flow copilot-instructions.md
Copilot instructions for bytedance/deer-flow, covering copilot onboarding instructions for deerflow, 1) repository summary, 2) runtime and toolchain requirements, 3) build/test/lint/run - verified command sequences and a. bootstrap and install.
intelligent-terminal agent-skills.instructions.md
Guidelines for creating high-quality Agent Skills for GitHub Copilot.
intelligent-terminal rust-localization.instructions.md
Instructions for microsoft/intelligent-terminal, covering localization instructions for rust wta (yaml locale files), file structure, file format, the en-us.yml source file and non-translatable token rules.
intelligent-terminal localization.instructions.md
Instructions for microsoft/intelligent-terminal, covering localization instructions for .resw resource files, components with localized resources, locale categories, authoritative locale list (from terminalapp) and adding or updating localized strings.
intelligent-terminal instructions.instructions.md
Guidelines for creating high-quality custom instruction files for GitHub Copilot.
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.