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.
git clone --depth 1 https://github.com/victorzhong0110/skill-evolutionnpx agentmods add commands/victorzhong0110/skill-evolution/bridge-monitorWrote 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/victorzhong0110/skill-evolution/bridge-monitor)<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.
<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>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.00000 | $0.01043 |
| Opus 5 | $0.00000 | $0.00522 |
| Sonnet 5 | $0.00000 | $0.00209 |
| Haiku 4.5 | $0.00000 | $0.00104 |
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.
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>.jsonwith{"id", "system", "messages", "temperature", "max_tokens", "model"} - Response format:
<uuid>.jsonwith{"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.
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.
- 12d ago First seen · 110 lines · 0 tokens per session scan A 086f548580d0
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.
Other commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
init
Scaffold a new MindBase project (v2 layout). Usage: /mb:init [template] [-- mission ...].
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
recall
Search past tool-call observations with BM25 ranking to answer "have I seen this before?" before re-deriving a fix or repeating a mistake. Enforces Law 1 (Research Before Executing).
requirement-review
A command that has several specialized agents review a requirements document and produce a revised version through a controlled workflow.