Borrowing it
Nothing to install: this file belongs to Keesan12/martin-loop. 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/Keesan12/martin-loop/main/AGENTS.mdgit clone --depth 1 https://github.com/Keesan12/martin-loopWrote 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/keesan12/martin-loop/agents-md)<a href="https://agentmods.dev/instructions/keesan12/martin-loop/agents-md"><img src="https://agentmods.dev/badge/instructions/keesan12/martin-loop/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/keesan12/martin-loop/agents-md"><img src="https://agentmods.dev/badge/instructions/keesan12/martin-loop/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.01674 | $0.01674 |
| Opus 5.5 | $0.00670 | $0.00670 |
| Sonnet 5.5 | $0.00335 | $0.00335 |
| Haiku 4.5 | $0.00167 | $0.00167 |
Grade A, and why
martin-loop 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MartinLoop Agent Operating Rules
This file is the sole durable operating guide for AI agents and automation working on MartinLoop.
Do not treat historical release notes, old audits, old handoff files, previous branches, terminal history, or prior session summaries as current instructions.
Repository authority
Development authority:
the private MartinLoop development repository
Public distribution repository:
Keesan12/martin-loop
All implementation starts, is reviewed, and is health-proven in the private development authority before public promotion begins.
The public repository is a distribution surface, not a development workspace.
Current-state authority
For current release/version state, use only:
- current Git branch / commit state;
package.json;packages/mcp/package.json;docs/release/VERSION-LEDGER.md;- current required release checks and current open PRs.
Do not infer current status from dates or claims embedded in old documentation.
Required development sequence
For product changes:
- start from current private
main; - create a private feature/fix branch;
- implement privately;
- run the required targeted and repo health checks;
- open a private PR;
- merge only after the change is reviewed and green;
- sync fresh private
main; - run the required private-main health proof;
- record the validated private release SHA;
- only then begin public promotion.
Never implement the real fix directly in the public repository.
Required release sequence
Use this order:
private authority → private health proof → clean public staging → promotion guard → public tests → public PR → public merge → publish → fresh-install proof → production E2E.
Do not reorder the sequence unless an existing release controller explicitly requires it.
Do not create an additional release phase merely because another agent used one previously.
Public promotion
Public promotion must be derived from the validated private release authority and the exact current public base.
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 · +2 lines · +67 tokens per session 2452ec51e4e4
- 1mo ago Changed · -54 lines · -392 tokens per session c12abccdb12d
- 1mo ago First seen · 252 lines · 1,999 tokens per session scan A 81df453c5098
martin-loop AGENTS.md is an instructions file published in the GitHub repository Keesan12/martin-loop (394 stars, last pushed yesterday), licensed Apache-2.0. It adds 1,674 tokens to every session, about $0.0067 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-30.
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.