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 instructions/marimo-team/marimo/copilot-instructionsgit clone --depth 1 https://github.com/marimo-team/marimoWhat 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.00091 | $0.00091 |
| Opus 5 | $0.00046 | $0.00046 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
marimo copilot-instructions.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 2d 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
Code Review Process
- If the PR seems AI-generated, you should request the contributor to:
- Provide screenshots of the fixed output (if possible)
- Check if it satisfies edge cases instead of just the direct problem it addresses.
For example, if there is a frontend change to make a border thicker, how does this look in run mode, app-view and edit-view? For a backend change, has the user tested different scenarios?
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.
- 2d ago First seen · 9 lines · 91 tokens per session scan A 1fdb681589e2
marimo copilot-instructions.md is an instructions file published in the GitHub repository marimo-team/marimo (22,550 stars, last pushed 2d ago), licensed Apache-2.0. It adds 91 tokens to every session, about $0.0005 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-30.
Other instructions, from other repositories
streamlit copilot-instructions.md
Copilot instructions for streamlit/streamlit, covering streamlit repo overview, tech stack, folder structure, shell & build policy and make commands.
FLAML copilot-instructions.md
Instructions for microsoft/FLAML, covering github copilot instructions for flaml, project overview, build and test commands, installation and basic installation.
cnsplots AGENTS.md
Instructions for faridrashidi/cnsplots, covering agents.md, working branch rules, implementation rules, validation rules and commit rules.
mlops-python-package AGENTS.md
AGENTS.md instructions for fmind/mlops-python-package, covering agents.md, project overview, setup & core commands, definition of done and conventions & idioms.
texera AGENTS.md
Instructions for apache/texera, covering agents.md, architecture map, amber breakdown, where things live and agent-specific rules.
texera CLAUDE.md
Instructions for apache/texera: Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to you under the Apache License, Version 2.0 (the…