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 rules/anshulixyz/multi-agent-loop-kit/00-repo-contextgit clone --depth 1 https://github.com/anshulixyz/multi-agent-loop-kitWrote 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/rules/anshulixyz/multi-agent-loop-kit/00-repo-context)<a href="https://agentmods.dev/rules/anshulixyz/multi-agent-loop-kit/00-repo-context"><img src="https://agentmods.dev/badge/rules/anshulixyz/multi-agent-loop-kit/00-repo-context.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 | $0.00132 | $0.00132 |
| Opus 5 | $0.00066 | $0.00066 |
| Sonnet 5 | $0.00026 | $0.00026 |
| Haiku 4.5 | $0.00013 | $0.00013 |
Grade A, and why
00-repo-context 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.
What it actually says
Repo context
This repo uses a multi-agent workflow with worktrees, path ownership, journals, proposals, approvals, and a Beacon loop layer.
Read in this order:
AGENTS.mdOPERATING_GUIDE.mdPROTOCOL.mdPROTOCOL.mdLOOP_RADAR.mdLOOP_MEMORY.md- your own journal in
agents-status/<codename>.md - relevant task briefs and approvals
Never assume you can edit a file until you check ownership.
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 · 22 lines · 132 tokens per session scan A b322ebc64f6a
00-repo-context is a cursor rule published in the GitHub repository anshulixyz/multi-agent-loop-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 132 tokens to every session, about $0.0007 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 cursor rules, from other repositories
cursor_rule_snippet
Latch decision-continuity gate for Cursor projects.
proxyshield-admin
ProxyShield admin UI conventions.
tech-stack
Cursor rule "tech-stack" from yu-iskw/coding-agent-fabric, covering tech stack, pnpm workspace & monorepo best practices, common commands, workspace protocol and dependency management.
less-is-more
Architecture-first, reduction-first workflow for code changes, debugging, refactoring, and cleanup. Use to trace the owning path, prefer no edit and subtraction before additions, replace obsolete behavior instead of layering around it, keep scope closed, refute your own diagnosis and fix before believing them, verify…
api
Prefer named exports.
project
Prefer explicit types.