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/ranaroussi/cc-bridge/claude-mdgit clone --depth 1 https://github.com/ranaroussi/cc-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/ranaroussi/cc-bridge/claude-md)<a href="https://agentmods.dev/instructions/ranaroussi/cc-bridge/claude-md"><img src="https://agentmods.dev/badge/instructions/ranaroussi/cc-bridge/claude-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.04243 | $0.04243 |
| Opus 5 | $0.02122 | $0.02122 |
| Sonnet 5 | $0.00849 | $0.00849 |
| Haiku 4.5 | $0.00424 | $0.00424 |
Grade A, and why
cc-bridge CLAUDE.md scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST http://localhost:8321/v1/messages \ How it starts
The opening of the file, as written. The whole thing — 724 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - CC-Bridge Development Guide
Project Overview
CC-Bridge is an HTTP service that provides 100% Anthropic API compatibility while using the official Claude Code CLI under the hood. This preserves OAuth access legitimately without authentication hacks.
Problem: Anthropic is shutting down third-party OAuth access. Apps using OAuth tokens directly now fail with:
LLM request rejected: This credential is only authorized for use with
Claude Code and cannot be used for other API requests.
Solution: Wrap claude -p (Claude CLI print mode) as an HTTP service. Let the official CLI handle authentication.
Quick Start
Prerequisites
-
Claude Code CLI installed:
npm install -g claude-code # Verify claude --version -
Claude Code authenticated:
claude setup-token # Follow OAuth flow or provide API key -
Go 1.21+:
go version
Development Setup
# Clone/create project
cd cc-bridge
# Build
make build
# Run server (default port 8321)
./build/ccbridge
# Or with custom port
./build/ccbridge --port 9000
# Test
curl -X POST http://localhost:8321/v1/messages \
-H "Content-Type: application/json" \
-d '{"model": "claude-sonnet-4-20250514", "messages": [{"role": "user", "content": "Hello"}]}'
Architecture
Client (Anthropic SDK)
↓ POST /v1/messages
Go HTTP Server (cc-bridge)
↓ spawn("claude", ["-p", ...])
Claude CLI
↓ OAuth or API key
Anthropic API
Key insight: We're not fighting OAuth - we're delegating auth to the official tool that's allowed to use it.
Implementation Guide
Phase 1: Non-Streaming MVP (10-12 hours)
Goal: Basic request/response works with Anthropic SDK
File Structure
cc-bridge/
├── src/
│ ├── main.go # HTTP server entry point
│ ├── handler.go # Request handler
│ ├── types.go # Type definitions
│ ├── cli.go # Execute claude -p
│ ├── mapper.go # Map API params ↔ CLI flags
│ ├── streaming.go # SSE streaming support
│ └── *_test.go # Tests
├── build/ # Compiled binaries
├── Makefile # Build commands
└── go.mod
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.
- 5d ago First seen · 724 lines · 4,243 tokens per session scan A 72586aa182b6
cc-bridge CLAUDE.md is an instructions file published in the GitHub repository ranaroussi/cc-bridge (53 stars, last pushed 7mo ago), licensed MIT. It adds 4,243 tokens to every session, about $0.0212 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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.