Borrowing it
Nothing to install: this file belongs to jamillazarev/multica-ops. 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/jamillazarev/multica-ops/main/AGENTS.mdgit clone --depth 1 https://github.com/jamillazarev/multica-opsWrote 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/jamillazarev/multica-ops/agents-md)<a href="https://agentmods.dev/instructions/jamillazarev/multica-ops/agents-md"><img src="https://agentmods.dev/badge/instructions/jamillazarev/multica-ops/agents-md/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/instructions/jamillazarev/multica-ops/agents-md"><img src="https://agentmods.dev/badge/instructions/jamillazarev/multica-ops/agents-md.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.07651 | $0.07651 |
| Opus 5.5 | $0.03060 | $0.03060 |
| Sonnet 5.5 | $0.01530 | $0.01530 |
| Haiku 4.5 | $0.00765 | $0.00765 |
Grade A, and why
multica-ops 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 1mo 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent entry point
This repository ships one skill: multica-ops — a Mops (Executive Advisor) that builds and runs an autonomous company of AI agents on Multica.
Using the skill? Whatever harness you are (Claude Code, Codex, Cursor, Windsurf, Antigravity CLI, …): read SKILL.md and follow it. Slash commands are a Claude Code plugin convenience; every flow works from natural language in any agent — "set up my team", "join this project", "status", "add a feature: …".
Requires the multica CLI on the machine, pointed at a workspace:
multica setup cloud, or multica setup self-host --server-url … for your own server.
Changing this repository? Read this part.
Two scripts guard it. Run them; they are fast and they have caught real defects:
bash scripts/preflight.sh # form: is the documentation well-made?
python3 scripts/verify.py --live # truth: do the commands and sources still exist?
A file named in prose is a link, not a backticked name. The link is the edge GitHub, Obsidian's
graph and preflight §4 can all see; a name is an edge only a reader infers. scripts/link-names.py --write makes the links and preflight §4d refuses the drift, with three kinds of name left as names.
The core — skills/mops/SKILL.md, loaded on every run, so a link there is paid every time.
A companion's name of another companion — a companion being any other root .md but README,
CHANGELOG, AGENTS and CLAUDE — because references stay one level deep from the core (preflight
§5c). And the files a project also carries — CLAUDE.md, LATER.md and the rest — which in
prose usually mean the project's own. A project's _ops/ has its own twin, scripts/link-ids.py
(BOOTSTRAP → Docs home).
What the automation cannot check — and what you must therefore read
The scripts verify shape and existence. They are blind to whether a paragraph is still correct, and every expensive defect this repo has shipped was of exactly that kind: a statement that parsed perfectly, linked correctly, and was false. So before you commit, read for these six things — as a human, or as an agent asked to review, but never assume a green hook covered them.
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.
- 1mo ago Changed · +27 lines · +439 tokens per session 9212c554e26b
- 1mo ago Changed · +16 lines · +370 tokens per session bcba01b0b03a
- 1mo ago Changed · +31 lines · +725 tokens per session 661a3c6d3e45
- 1mo ago Changed · +5 lines · +108 tokens per session 70b034af2c5f
- 1mo ago First seen · 314 lines · 6,009 tokens per session scan A 3828d3341a9f
multica-ops AGENTS.md is an instructions file published in the GitHub repository jamillazarev/multica-ops (17 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7,651 tokens to every session, about $0.0306 per session on Opus 5.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
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.