Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/sirasaki-konoha/mop/agents-mdgit clone --depth 1 https://github.com/sirasaki-konoha/mopWrote 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/sirasaki-konoha/mop/agents-md)<a href="https://agentmods.dev/instructions/sirasaki-konoha/mop/agents-md"><img src="https://agentmods.dev/badge/instructions/sirasaki-konoha/mop/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.00793 | $0.00793 |
| Opus 5 | $0.00396 | $0.00396 |
| Sonnet 5 | $0.00159 | $0.00159 |
| Haiku 4.5 | $0.00079 | $0.00079 |
Grade A, and why
mop 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 4d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex guidance for MOP
This repository provides MOP, a shared Streamable HTTP MCP server for recording
and coordinating multi-agent work. The server is available to Codex in this
project as mop when .venv has been prepared and src/http_entry.py is
running at http://127.0.0.1:8765/mcp.
When to use MOP
Use MOP when the user explicitly requests multi-agent orchestration, task tracking, agent-to-agent communication, artifact review, or result merging. Do not use it for ordinary small edits, questions, or single-agent tasks solely to create process records.
MOP records workflow state; assign_agent does not start an agent. Live
messages are shared only when every participant connects to the same HTTP
server process. A delivered message does not start or wake an idle model by
itself; the receiving client must call get_agent_inbox or have an active
wait_for_agent_message call. Only assign work that has a real execution plan,
and perform the work with Codex's available collaboration mechanisms as
appropriate.
MOP workflow
- Call
list_registered_agents. Register Codex withregister_agentonly if no suitable Codex agent is already registered. Use a stable ID such ascodexand describe the actual role for this task. - Call
decompose_taskonce for the user request. Keep the resulting task ID and use its subtask IDs; do not create duplicate root tasks for retries. - Before parallel work begins, use
assign_agentto record the intended owner of each actionable subtask. Keep assignments aligned with actual agents or roles. - Use
agent_communicatefor decisions, blockers, handoffs, or review requests that need to remain in the task record. Include the relevanttask_id. - After completing a meaningful deliverable, call
submit_artifactwith its real repository path, an accurate content summary, and the appropriate artifact type. Never submit placeholder artifacts. - Use
get_task_statusbefore reporting progress or starting final integration. Review submitted code withreview_codewhen a review is in scope; address rejected work before merging. - Call
merge_resultsonly after the needed subtasks and artifacts are ready. Report the merge result and any remaining blockers truthfully.
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.
- 4d ago First seen · 70 lines · 793 tokens per session scan A cb9388893996
mop AGENTS.md is an instructions file published in the GitHub repository sirasaki-konoha/mop (0 stars, last pushed 1mo ago), licensed MIT. It adds 793 tokens to every session, about $0.0040 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).
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.
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).