Borrowing it
Nothing to install: this file belongs to Ichliebedich1/mimo-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/Ichliebedich1/mimo-bridge-mcp/master/AGENTS.mdgit clone --depth 1 https://github.com/Ichliebedich1/mimo-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/ichliebedich1/mimo-bridge-mcp/agents-md)<a href="https://agentmods.dev/instructions/ichliebedich1/mimo-bridge-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ichliebedich1/mimo-bridge-mcp/agents-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.01008 | $0.01008 |
| Opus 5 | $0.00504 | $0.00504 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
mimo-bridge-mcp AGENTS.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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Instructions
Stack And Commands
- Runtime: Node.js + TypeScript + MCP SDK. Production collaboration uses the shared local daemon over Streamable HTTP; STDIO remains a compatibility/test entry.
- Build:
npm.cmd run build - Admin UI build:
cd apps/admin-ui; npm.cmd run build - Local daemon build:
cd apps/local-daemon; npm.cmd run build - Portable package:
npm.cmd run package:portable - Installer package:
npm.cmd run package:installer - Release validation:
npm.cmd run validate:release - Normal regression:
node --test (rg --files tests -g '*.test.mjs' | Where-Object { $_ -notmatch 'runner-integration\.test\.mjs$' }) - Do not run
tests/runner-integration.test.mjsin the normal suite; it is a tracked hanging P2 test debt.
Shared Collaboration Runtime
- Start the daemon with
powershell -ExecutionPolicy Bypass -File apps/local-daemon/start-local.ps1. - Codex
mimo_bridgemust point tohttp://127.0.0.1:3210/mcpso the UI and Codex share one queue, running-task registry, and token manager. - Do not run the production STDIO bridge beside the daemon for task execution.
- Config transport changes take effect only after restarting Codex or opening a new Codex session.
- The UI handoff control copies a bounded review prompt and opens
codex://threads/new; it does not silently submit a message. mimo_delete_taskis permanent: only deleteaccepted,failed,cancelled, orabandonedtasks after confirming they have no Worktree. Browser actions require the UI confirmation dialog.
Mandatory Low-Context Review
When reviewing a MiMo task, call mimo_get_task in this order:
- Start with
detail_level="review"and a smallmax_charsbudget. - Check editable paths, changed files, out-of-bounds report, diff stat, test result, and risk flags.
- If no risk is present, decide whether to merge without reading full files or logs.
- If risk is present, request only the relevant
diff_paths,file_paths, or log tail. - Use
detail_level="full"only for explicit debugging and record why escalation was necessary.
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 · 61 lines · 1,008 tokens per session scan A e239515ea146
mimo-bridge-mcp AGENTS.md is an instructions file published in the GitHub repository Ichliebedich1/mimo-bridge-mcp (3 stars, last pushed 27d ago), licensed MIT. It adds 1,008 tokens to every session, about $0.0050 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
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).
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.
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).
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.