Borrowing it
Nothing to install: this file belongs to grizzly2005/bidirectional-bridge-claude-codex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/grizzly2005/bidirectional-bridge-claude-codex/main/.agents/skills/using-bridge/SKILL.mdgit clone --depth 1 https://github.com/grizzly2005/bidirectional-bridge-claude-codexWrote 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/skills/grizzly2005/bidirectional-bridge-claude-codex/using-bridge)<a href="https://agentmods.dev/skills/grizzly2005/bidirectional-bridge-claude-codex/using-bridge"><img src="https://agentmods.dev/badge/skills/grizzly2005/bidirectional-bridge-claude-codex/using-bridge/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/skills/grizzly2005/bidirectional-bridge-claude-codex/using-bridge"><img src="https://agentmods.dev/badge/skills/grizzly2005/bidirectional-bridge-claude-codex/using-bridge.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.00081 | $0.03757 |
| Opus 5.5 | $0.00032 | $0.01503 |
| Sonnet 5.5 | $0.00016 | $0.00751 |
| Haiku 4.5 | $0.00008 | $0.00376 |
Grade A, and why
using-bridge 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 18d 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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use the Bridge
Use the bridge as a coordination layer, not as a reason to involve another agent. Keep the current native client responsible for the user request; delegate only a bounded subtask whose expected value exceeds startup, context, and verification overhead.
Choose the path
skills/using-bridge/ is the versioned source. Generate the client mirrors with
node scripts/sync-bridge-skill.mjs --write; check them with --check.
Edit the source rather than a client mirror.
- Delegate: assign one independent, verifiable subtask to the other runtime.
- Review: ask the other runtime for a bounded, usually read-only, independent review.
- Recover: resume one known stranded task in place after quota, timeout, crash, or process interruption.
- Observe: inspect telemetry or events only when the user requests them, during dogfooding, or for diagnosis.
- Track visually: on a request such as “active le suivi de délégation”, open the opt-in view before a blocking delegation; read tracking-ui.md.
- Do not use the bridge: complete trivial, tightly coupled, or cheaper single-agent work locally.
If native bridge tools are absent, report that limitation and use read-only offline sources for observation when useful. Configuration files and an offline review do not prove a live bridge delegation. Do not replace missing MCP access with a direct worker CLI call.
If this session is already a delegated worker with a supplied task_id, scope, expected deliverable, and verification criteria, complete that contract. Do not create a new root or delegate again unless the contract explicitly permits it.
Tracking does not create a task, confer manager authority, or trigger another model. Keep UI polling in the widget, never in repeated model turns. Closing or disabling the view leaves workers running; cancellation remains a separate explicit request.
Decide whether to delegate
Delegate only when all are true:
- The child task is independently understandable from a compact contract.
- Its write scope is disjoint, or it is read-only.
- Its output and verification criteria are explicit.
- The other runtime adds distinct implementation, diagnosis, review, or research value.
- The manager can consume and verify the result without prolonged back-and-forth.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 18d ago Changed · +39 lines 48ffdef6d3b0
- 26d ago Changed · +5 lines 028697398f29
- 27d ago Changed · +58 lines cf17fa2574e2
- 2mo ago First seen · 186 lines · 81 tokens per session scan A 52e51c8b4c08
using-bridge is a skill published in the GitHub repository grizzly2005/bidirectional-bridge-claude-codex (1 stars, last pushed 5d ago), licensed MIT. It adds 81 tokens to every session and 3,757 once invoked, about $0.0003 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-31.
Other skills, from other repositories
takt
A workflow engine that runs a task through a sequence of steps defined in a YAML file, using separate coding agents for the work.
company-product-context
Compiles comprehensive company product context from PDF documents, web research, and industry knowledge.
codebase-context-extractor
This skill provides a comprehensive context extraction system for large codebases. It intelligently analyzes code structure, dependencies, and relationships to extract relevant context for understanding, debugging, or modifying code.
skill-creator
Generates Anthropic Skills with complete workflow including GitHub PR creation and local download verification.
Research Synthesis Workflow
A step-by-step guide to synthesizing research from multiple sources into a coherent summary.
Ability Generator
This skill generates markdown skill templates to be later used.