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 skills/marimo-team/marimo/marimo-pairnpx skills add marimo-team/marimo --skill marimo-pairgit 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.00057 | $0.02580 |
| Opus 5 | $0.00028 | $0.01290 |
| Sonnet 5 | $0.00011 | $0.00516 |
| Haiku 4.5 | $0.00006 | $0.00258 |
Grade A, and why
marimo-pair 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- marimo-pair — 88% identical, 138 lines differ
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
marimo is a reactive Python runtime for building reproducible Python programs
(marimo notebooks). Cells are connected by the variables they define and
reference. Running a cell re-executes dependents in dataflow order. The active
runtime holds the kernel namespace, cell state, and dataflow graph. The
notebook (.py file) is the artifact the kernel writes from that state while a
session is running.
A user interacts with the same runtime via a notebook UI with cells, outputs, and widgets.
WARNING. The active runtime is the source of truth. You are working inside
the user's live notebook session. The kernel — not the .py file on disk —
holds the truth about cells, variables, and the dataflow graph. Make every
notebook change through marimo._code_mode (cm); direct file edits WILL NOT
reach the live kernel or user, and the kernel may overwrite them on save.
Reading disk is fine, but prefer ctx.cells[...].code for current cell code.
WARNING. Every notebook edit goes through code mode — no exceptions. When
the user asks you to change the notebook (add, edit, delete, or run a cell;
rename; change a value or a package), you MUST make that change through
marimo._code_mode (cm) by running it with the execute_code tool. There is
no separate file-editing path — execute_code + cm is the only way to reach
the user's running session. Running ad-hoc Python with execute_code to
explore or test is fine; persisting any change to the notebook is only ever
done via cm.
Running Code in the Kernel
You are already attached to the user's running notebook — there is nothing to
connect to or start. Use the execute_code tool to run Python in that kernel,
passing your Python as the code argument. Everything you do — inspecting
state, testing transformations, and persisting changes via cm — runs through
execute_code in the scratchpad (see below).
Required First Kernel Command
Start every code-mode session with this dedicated execute_code call:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 278 lines · 57 tokens per session scan A 7ee57b94324e
marimo-pair is a skill published in the GitHub repository marimo-team/marimo (22,550 stars, last pushed 2d ago), licensed Apache-2.0. It adds 57 tokens to every session and 2,580 once invoked, about $0.0003 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 skills, from other repositories
cnsplots
Create, revise, and troubleshoot publication-ready scientific plots in Python with cnsplots, including distribution, regression, heatmap, genomics, survival, set, flow, and multi-panel figures. Use when a user asks for cnsplots code, Cell/Nature/Science-style visualization, precise pixel-sized figures, statistical…
addressing-pr-review-comments
Address all valid review comments on a PR for the current branch in the streamlit/streamlit repo. Covers both inline review comments and general PR (issue) comments. Use when a PR has reviewer feedback to address, including code changes, style fixes, and documentation updates.
generating-changelog
Generates polished website release notes between two git tags for docs.streamlit.io. Use when preparing a new Streamlit release or reviewing changes between versions.
understanding-streamlit-architecture
Explains Streamlit's internal architecture including backend runtime, frontend rendering, and WebSocket communication. Use when debugging cross-layer issues, understanding how features work end-to-end, planning architectural changes, or onboarding to the codebase. Covers ForwardMsg/BackMsg protocol, script rerun…
debugging-streamlit
Debug Streamlit frontend and backend changes using make debug with hot-reload. Use when testing code changes, investigating bugs, checking UI behavior, or needing screenshots of the running app.
fixing-flaky-e2e-tests
Diagnose and fix flaky Playwright e2e tests. Use when tests fail intermittently, show timeout errors, have snapshot mismatches, or exhibit browser-specific failures.