Borrowing it
Nothing to install: this file belongs to lootlog/monorepo. 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/lootlog/monorepo/main/AGENTS.mdgit clone --depth 1 https://github.com/lootlog/monorepoWrote 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/lootlog/monorepo/agents-md)<a href="https://agentmods.dev/instructions/lootlog/monorepo/agents-md"><img src="https://agentmods.dev/badge/instructions/lootlog/monorepo/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/lootlog/monorepo/agents-md"><img src="https://agentmods.dev/badge/instructions/lootlog/monorepo/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.04151 | $0.04151 |
| Opus 5.5 | $0.01660 | $0.01660 |
| Sonnet 5.5 | $0.00830 | $0.00830 |
| Haiku 4.5 | $0.00415 | $0.00415 |
Grade A, and why
monorepo 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 5d 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 — 380 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lootlog
Lootlog is an open-source Margonem companion that connects an in-game client, a shared web workspace, and Discord. It turns supported gameplay events into current, durable information for players and organized groups without requiring them to copy timers, loot records, or coordination state by hand.
The primary daily user is an active member of an organized Margonem group. A leader, deputy, or tactician usually makes the adoption decision, but every member must receive useful in-game feedback rather than acting only as a data source.
What Lootlog must protect
1. Trust the signal
Accepted durable records must not disappear silently, and retries must not create unintended duplicates. Show degraded or stale state instead of presenting it as current truth.
2. Keep Margonem fast
Normal play must not feel slower with Lootlog enabled. Keep game-client work bounded; a client performance regression is a release blocker.
3. Isolate Organizations
The Organization is the top-level security boundary. Apply its access policy to base records, derived views, delivery paths, and metadata.
4. Complete the connected workflow
A change is incomplete when it works on one relevant surface but fails on another. Account for the Game client, Web app, Discord bot, public surfaces, installation methods, deployed contracts, and generated clients as applicable.
Resolve architectural trade-offs in this order:
- Do not interfere with Margonem or lose accepted durable data.
- Preserve Game client performance.
- Preserve security and Organization isolation.
- Preserve real-time reliability.
- Control infrastructure cost.
- Preserve development speed and maintainability.
- Preserve abstract future flexibility.
Project principles
Prefer ambitious outcomes and simple systems. Understand the real constraint, then implement the smallest complete model that makes correct behavior unsurprising. Remove accidental complexity instead of preserving it, and avoid machinery justified only by a possible future need.
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.
- 5d ago Changed · +4 lines · +75 tokens per session 698959437900
- 6d ago Changed · +5 lines · +78 tokens per session 92cc9d1fae57
- 7d ago Changed · +2 lines · +39 tokens per session f367b41b65de
- 17d ago Changed · +2 lines · +35 tokens per session 8b5d561bde63
- 22d ago Changed · -2 lines · -29 tokens per session 778056faede5
- 28d ago Changed · +4 lines · +68 tokens per session c9ec6390da9c
- 1mo ago Changed · +7 lines · +105 tokens per session 40ce4fbdbe13
- 1mo ago Changed · +11 lines · +185 tokens per session cf4f32a48baa
- 1mo ago Changed · +24 lines · +297 tokens per session 2f31c2a7366e
- 1mo ago First seen · 323 lines · 3,298 tokens per session scan A 764e71ff5f33
monorepo AGENTS.md is an instructions file published in the GitHub repository lootlog/monorepo (29 stars, last pushed yesterday), licensed MIT. It adds 4,151 tokens to every session, about $0.0166 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.