bridge-monitor

bridge-monitor is a command for Claude Code from victorzhong0110/skill-evolution. It costs 0 tokens per session (1,043 once invoked), scanned A, original, MIT.

A bridge-monitor command that processes completion requests created by the skill-evolution framework. It uses separate agent tasks to produce JSON responses for those requests.

In plain words
What is it for?
Use it to watch the framework's request directory, handle pending JSON requests, and write matching responses until the queue stays empty or you stop it.
Why use it?
It lets the framework obtain language-model completions without launching separate Claude command-line processes for every request.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions Claude Code.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is python scripts/bridge_monitor.py list.

Good fit Use it to watch the framework's request directory, handle pending JSON requests, and write matching responses until the queue stays empty or you stop it.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/victorzhong0110/skill-evolution
agentmods
npx agentmods add commands/victorzhong0110/skill-evolution/bridge-monitor

Made for: Claude Code.

Wrote 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.

agentmods badge for bridge-monitor

README.md
[![agentmods](https://agentmods.dev/badge/commands/victorzhong0110/skill-evolution/bridge-monitor/github.svg)](https://agentmods.dev/commands/victorzhong0110/skill-evolution/bridge-monitor)
Your own site
<a href="https://agentmods.dev/commands/victorzhong0110/skill-evolution/bridge-monitor"><img src="https://agentmods.dev/badge/commands/victorzhong0110/skill-evolution/bridge-monitor/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.

agentmods 80×15 button for bridge-monitor

Your own site · 80×15
<a href="https://agentmods.dev/commands/victorzhong0110/skill-evolution/bridge-monitor"><img src="https://agentmods.dev/badge/commands/victorzhong0110/skill-evolution/bridge-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,043 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01043
Opus 5 $0.00000 $0.00522
Sonnet 5 $0.00000 $0.00209
Haiku 4.5 $0.00000 $0.00104

Measured 12d ago against content hash 086f548580d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

bridge-monitor 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 12d 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.

.claude/commands/bridge-monitor.md · 110 lines

How it starts

The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bridge Monitor — LLM Request Processor

You are a bridge monitor for the skill-evolution framework. Your job is to process LLM completion requests that the Python framework writes to a bridge directory, using Agent sub-tasks with clean context.

Background

The skill-evolution framework (python -m skill_evolution.cli meta-evolve -p bridge) writes LLM requests as JSON files. Instead of spawning expensive claude -p subprocesses, you process each request by spawning an Agent with only the system prompt and user prompt from the request — no other context contamination.

Bridge Protocol

  • Request dir: /tmp/skill-evolution-bridge/requests/
  • Response dir: /tmp/skill-evolution-bridge/responses/
  • Request format: <uuid>.json with {"id", "system", "messages", "temperature", "max_tokens", "model"}
  • Response format: <uuid>.json with {"content", "model", "input_tokens", "output_tokens", "stop_reason"}

Instructions

Execute the following loop until no more requests arrive for 60 seconds or the user tells you to stop.

Step 1: Check for pending requests

Run:

python scripts/bridge_monitor.py list

If output is NO_PENDING, wait 3 seconds and check again. After 60 seconds of consecutive NO_PENDING, the evolution has likely finished — print a summary and stop.

Step 2: For each pending request

Read the full request:

python scripts/bridge_monitor.py read <request_id>

Extract the system and messages fields from the JSON.

Step 3: Spawn an Agent to generate a clean response

Spawn an Agent with subagent_type: "claude" and model: "sonnet".

The Agent prompt MUST follow this exact template:

You are an LLM completion endpoint. You will receive a system prompt and a user prompt. Generate a response as if you were a fresh LLM instance with ONLY those two inputs. No meta-commentary — output ONLY the raw response.

=== SYSTEM PROMPT ===
{paste the full system field here}

=== USER PROMPT ===
{paste the full user message content here}

=== INSTRUCTIONS ===
Generate your response now. Output ONLY the response content, nothing else. Follow any output format specified in the user prompt exactly.

Read the full file on GitHub · 110 lines

Changes

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.

  1. 12d ago First seen · 110 lines · 0 tokens per session scan A 086f548580d0

Subscribe to this mod's changes

bridge-monitor is a command published in the GitHub repository victorzhong0110/skill-evolution (11 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,043 tokens. 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.