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 commands/anshulixyz/multi-agent-loop-kit/ownershipgit 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/commands/anshulixyz/multi-agent-loop-kit/ownership)<a href="https://agentmods.dev/commands/anshulixyz/multi-agent-loop-kit/ownership"><img src="https://agentmods.dev/badge/commands/anshulixyz/multi-agent-loop-kit/ownership.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.00012 | $0.00165 |
| Opus 5 | $0.00006 | $0.00082 |
| Sonnet 5 | $0.00002 | $0.00033 |
| Haiku 4.5 | $0.00001 | $0.00016 |
Grade A, and why
ownership 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 3d 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
Run the ownership check helper (use during PR review).
Run, optionally passing a base branch in $ARGUMENTS:
bash "${CLAUDE_PLUGIN_ROOT}/bin/loop-ownership" $ARGUMENTS
This lists the files changed vs the base branch. Compare them against the ownership rules in
AGENTS.md and .cursor/rules/01-ownership.mdc, and flag any file an agent touched that it
does not own. The helper is intentionally conservative — it lists; you do the judging.
(If the plugin's bin/ is on your PATH, loop-ownership [base-branch] is the same command.)
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.
- 3d ago First seen · 19 lines · 12 tokens per session scan A bf5d6b6cf6e8
ownership is a command published in the GitHub repository anshulixyz/multi-agent-loop-kit (5 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 165 once invoked, about $0.0001 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 commands, from other repositories
ctx
Search agent history or trace code to its original agent session.
unlatch
Confirmed toggle for latch Unlatched mode.
latch-heal
Nightly heal — integrity sweep + three-pass contradiction resolver.
latch-gate-report
Read-only report over recent latch gate activity.
handoff
Export a Waybill Bundle by default, or import one when requested.
krimto-status
Show the current state of Krimto memory — total facts, scope breakdown, recent writes, and index health.