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.
git clone --depth 1 https://github.com/raysonmeng/agent-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/commands/raysonmeng/agent-bridge/init)<a href="https://agentmods.dev/commands/raysonmeng/agent-bridge/init"><img src="https://agentmods.dev/badge/commands/raysonmeng/agent-bridge/init/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/raysonmeng/agent-bridge/init"><img src="https://agentmods.dev/badge/commands/raysonmeng/agent-bridge/init.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00514 |
| Opus 5.5 | $0.00005 | $0.00206 |
| Sonnet 5.5 | $0.00003 | $0.00103 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
init 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 1mo 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
Bootstrap or update AgentBridge's project-local configuration in this workspace.
Follow these rules:
- Work only inside
.agentbridge/. - Do not install plugins or modify
.claude/settings.jsonhere. Plugin setup belongs to terminal workflows:agentbridge initattempts best-effort plugin installation, andagentbridge devhandles local marketplace registration/sync. - Preserve user edits when the files already exist. Update only the fields the user asked to change.
- Keep
.agentbridge/config.jsonvalid JSON. - Keep
.agentbridge/collaboration.mdhuman-editable and concise.
If .agentbridge/config.json is missing, create it with this default template:
{
"version": "1.0",
"daemon": {
"port": 4500,
"proxyPort": 4501
},
"agents": {
"claude": {
"role": "Reviewer, Planner",
"mode": "push"
},
"codex": {
"role": "Implementer, Executor"
}
},
"markers": ["IMPORTANT", "STATUS", "FYI"],
"turnCoordination": {
"attentionWindowSeconds": 15,
"busyGuard": true
},
"idleShutdownSeconds": 30
}
If .agentbridge/collaboration.md is missing, create it with this default template:
# Collaboration Rules
## Roles
- Claude: Reviewer, Planner, Hypothesis Challenger
- Codex: Implementer, Executor, Reproducer/Verifier
## Thinking Patterns
- Analytical/review tasks: Independent Analysis & Convergence
- Implementation tasks: Architect -> Builder -> Critic
- Debugging tasks: Hypothesis -> Experiment -> Interpretation
## Communication
- Use explicit phrases: "My independent view is:", "I agree on:", "I disagree on:", and "Current consensus:"
- Tag messages with [IMPORTANT], [STATUS], or [FYI]
## Review Process
- Cross-review: author never reviews their own code
- All changes go through feature/fix branches + PR
- Merge via squash merge
## Custom Rules
<!-- Add project-specific collaboration rules here -->
When you finish, briefly summarize what changed and point the user to the two files you updated.
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.
- 1mo ago First seen · 71 lines · 13 tokens per session scan A afa9e3c00a4d
init is a command published in the GitHub repository raysonmeng/agent-bridge (394 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 514 once invoked, about $0.0001 per session on Opus 5.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 commands, from other repositories
speckit.specjudge.recommend
Recommend the model that fits this feature's tasks, with the fragment of the spec behind every level.
tree-ring-capture
Capture a concise validated lesson decision warning or preference in Tree Ring Memory.
tree-ring-audit
Audit consolidate or forget stale sensitive or superseded Tree Ring Memory entries.
tree-ring-dox-sync
Preview and synchronize DOX-style AGENTS.md guidance as source-linked Tree Ring memory.
tree-ring-certify
Generate Tree Ring harness or recall-quality evidence without confusing it with the full framework release suite.
tree-ring-recall
Recall durable Tree Ring Memory context before starting or resuming work.