Borrowing it
Nothing to install: this file belongs to Lloydm15/agent-bridge-mcp. 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/Lloydm15/agent-bridge-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/Lloydm15/agent-bridge-mcpWrote 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/lloydm15/agent-bridge-mcp/claude-md)<a href="https://agentmods.dev/instructions/lloydm15/agent-bridge-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/lloydm15/agent-bridge-mcp/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.1 | $0.00612 | $0.00612 |
| Opus 5 | $0.00306 | $0.00306 |
| Sonnet 5 | $0.00122 | $0.00122 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
agent-bridge-mcp CLAUDE.md 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 7d 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mevoric
Unified Memory + Agent Bridge. Replaced 3 separate systems (newcode-memory, agent-bridge, Python hooks) with ONE npm package.
Tools (12)
retrieve_memories, store_conversation, judge_memories, register_agent, list_agents, send_message, read_messages, broadcast, share_context, get_context, save_checkpoint, load_checkpoint
Hooks (3)
--bootstrap-context(SessionStart)--capture-prompt+--check-messages(UserPromptSubmit)--ingest(Stop)
Setup
npx mevoric init --server http://192.168.2.100:3100 — handles global config, project configs, hooks, permissions, legacy pip cleanup
How It Runs
- Hub runs on the Linux server (192.168.2.100:4100) via pm2 as
mevoric-hub- Start:
ssh to server → pm2 start hub.mjs --name mevoric-hub - Auto-restarts on crash and on server reboot (pm2 saved)
- Start:
- MCP client (
server.mjs) runs locally on Lloyd's PC via Claude Code's MCP config- Path:
C:/dev/mcp-tools/mevoric/server.mjs - Memory server:
http://192.168.2.100:3100(Cortex —/api/retrieveworks,/api/ingestcurrently returns{"status":"skipped","reason":"mevoric-ingest disabled to reduce memory bloat"}) - Hub (legacy):
http://192.168.2.100:4100— the MCP client still points here via env var, but the runner now talks to Cortex council on:3100/api/council/* - Data dir:
C:\Users\lloyd\AppData\Local\agent-bridge
- Path:
Infrastructure
- Memory server: 192.168.2.100:3100 (Cortex API —
/ingest,/retrieve,/feedbackendpoints). Mevoric is just the client. - Hub: 192.168.2.100:4100 (pm2: mevoric-hub, handles agent messaging + knowledge sharing)
- Data dir:
C:\Users\lloyd\AppData\Local\agent-bridge(legacy path preserved) - Tests:
cd c:\dev\mcp-tools\mevoric && node --test test/stress.test.mjs(50 stress tests) - Runner:
start-runner.batis registered as a Windows scheduled task ("Mevoric Runner", auto-start at logon) — runsrunner.mjswhich polls Cortex council every 10s and wakes Claude CLI for direct messages
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.
- 7d ago First seen · 32 lines · 612 tokens per session scan A c5923d1d04f4
agent-bridge-mcp CLAUDE.md is an instructions file published in the GitHub repository Lloydm15/agent-bridge-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 612 tokens to every session, about $0.0031 per session on Opus 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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).
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).
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.
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.