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/kununu/agent-bridge/agents-mdgit clone --depth 1 https://github.com/kununu/agent-bridgeWhat 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.00139 | $0.00139 |
| Opus 5 | $0.00069 | $0.00069 |
| Sonnet 5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
Grade A, and why
agent-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 3d 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.
What it actually says
agent-bridge — notes for agents working in this repo
Keep the docs in sync with the code. When you change how the bridge behaves — e.g.
scripts/ (bridge.sh, render.py, adapter.py, meta.py), scripts/adapters/*.json,
or SKILL.md — update README.md and any affected references/*.md in the same change.
Docs must match actual behavior. Keep them short, accurate, concise. No one wants to read pages of AI slop, so before expanding and growing the doc ensure that what you're writing is actually valuable.
Stale docs are worse than none.
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.
- 3d ago First seen · 10 lines · 139 tokens per session scan A d56b43fe4d2d
agent-bridge AGENTS.md is an instructions file published in the GitHub repository kununu/agent-bridge (14 stars, last pushed 11d ago), licensed MIT. It adds 139 tokens to every session, about $0.0007 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
Waza AGENTS.md
AGENTS.md instructions for tw93/Waza, covering waza agent guide, project, repository map, health implementation ownership and commands.
simu CLAUDE.md
Instructions for chkhm/simu, covering claude.md, project, commands, source layout and architecture.
Waza CLAUDE.md
Claude Code instructions for tw93/Waza, a project described as: 🥷 Engineering habits you already know, turned into skills Claude can run.
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.