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/adrunkhuman/marimo-opencode-skill/marimo-notebooknpx skills add adrunkhuman/marimo-opencode-skill --skill marimo-notebookgit clone --depth 1 https://github.com/adrunkhuman/marimo-opencode-skillWhat 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.00043 | $0.04214 |
| Opus 5 | $0.00022 | $0.02107 |
| Sonnet 5 | $0.00009 | $0.00843 |
| Haiku 4.5 | $0.00004 | $0.00421 |
Grade A, and why
marimo-notebook 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.
How it starts
The opening of the file, as written. The whole thing — 686 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Marimo Notebook Skill
Running & Editing
# Edit interactively in browser
uv run marimo edit <notebook.py>
# Run as web app (code hidden)
uv run marimo run <notebook.py>
# Run as plain script (non-interactive, for testing/CI)
uv run <notebook.py>
# Lint for common mistakes — always run before handing back to user
uvx marimo check <notebook.py>
uvx marimo check --fix <notebook.py>
When to use this skill
- Creating .py notebook files for interactive data exploration
- Building reactive dashboards/apps with marimo
- Converting Jupyter notebooks (.ipynb) to marimo
Ask clarifying questions if:
- User mentions "Cell.run()", "reusable cells", or "testing cells" (API use case, different patterns)
- User wants to "pass variables between cells" with parameters/returns (wrong mental model)
File Format
Marimo notebooks are .py files. Each cell is a function decorated with @app.cell.
Marimo resolves dependencies via static analysis of the cell body — it reads what
variables you assign and reference, then builds a DAG automatically.
When marimo saves, it auto-generates function parameters and return tuples as
serialization metadata. You don't need to manage these yourself. Write def _():
for all cells. Marimo handles the rest.
# /// script
# requires-python = ">=3.12"
# dependencies = [
# "marimo",
# "pandas",
# "numpy",
# ]
# ///
import marimo
__generated_with = "0.19.7"
app = marimo.App(width="medium")
@app.cell
def _():
import marimo as mo
import pandas as pd
import numpy as np
@app.cell
def _():
# df is automatically available to all other cells
df = pd.read_parquet("data/input.parquet")
@app.cell
def _():
# Reference df directly — marimo knows the dependency
filtered = df[df["value"] > threshold.value]
mo.md(f"**{len(filtered)} rows** after filtering")
if __name__ == "__main__":
app.run()
PEP 723 inline dependencies (# /// script block) are added automatically by
marimo edit --sandbox but should always be present. They enable --sandbox
mode for isolated execution.
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 · 686 lines · 43 tokens per session scan A 97755b3c5353
marimo-notebook is a skill published in the GitHub repository adrunkhuman/marimo-opencode-skill (5 stars, last pushed 5mo ago), licensed MIT. It adds 43 tokens to every session and 4,214 once invoked, about $0.0002 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 skills, from other repositories
hipocampo-protocol
Protocolo de memoria dual con Sparse Selective Caching (SSC) v4.0 + Memory Graph + Compresión Híbrida. Persiste en memoriavectorial y memoryitems con búsqueda semántica progresiva. Cargar al inicio de cada sesión.
smart-git-commit
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
appium-python-expert
Specialist skill for mobile E2E testing with Appium 2.x + Python (pytest) for Android and iOS. Use this skill whenever the user asks about: setting up Appium with Python, writing mobile test cases, configuring Android/iOS drivers (UIAutomator2, XCUITest), implementing Page Object Model for mobile, running tests with…
selenium-cucumber-expert
Use when writing E2E tests with Selenium WebDriver and Cucumber BDD in Java, setting up BDD test infrastructure with Maven or Gradle, writing Gherkin feature files, implementing step definitions in Java, configuring Page Object Model or Screenplay Pattern, setting up parallel execution, generating ExtentReports or…
diffler
Generate and deliver a graded comprehension quiz from the current Git branch diff, either in the local terminal or through Google Forms. Use when a user asks to prove, test, or verify understanding of branch changes, a feature branch, or a pull request.
playwright-cucumber-expert
Use when writing E2E tests with Cucumber BDD and Playwright, setting up BDD test infrastructure, writing Gherkin feature files, implementing step definitions, configuring hooks and World, or integrating Cucumber with CI/CD. Invoke for Cucumber, BDD, Gherkin, feature files, step definitions, Given When Then, hooks…