Marin is an open-source research program, software platform, and community for developing foundation models such as large language models. Researchers use it for data preparation, tokenization, pretraining, posttraining, evaluation, and related experiments, including work on audio-text, DNA, and protein models. The catalogue entries are add-ons that support workflows around Marin.
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/marin-community/marin/refresh-forknpx skills add marin-community/marin --skill refresh-forkgit clone --depth 1 https://github.com/marin-community/marinWrote 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/skills/marin-community/marin/refresh-fork)<a href="https://agentmods.dev/skills/marin-community/marin/refresh-fork"><img src="https://agentmods.dev/badge/skills/marin-community/marin/refresh-fork.svg" alt="Measured on agentmods" 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 | $0.00027 | $0.04074 |
| Opus 5 | $0.00014 | $0.02037 |
| Sonnet 5 | $0.00005 | $0.00815 |
| Haiku 4.5 | $0.00003 | $0.00407 |
Grade A, and why
refresh-fork 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Refresh a fork
Read AGENTS.md. Rebase the fork overlay onto <branch>-next, validate that
staged tip, re-pin Marin, and prepare protected-branch promotion. An unattended
run opens a draft Marin PR and names the required admin promotion; it never
force-moves the stable branch.
Refresh a group as one unit and one PR. Per-fork guidance lives beside this
file: docs/vllm.md covers the vllm/tpu-inference group and the GPU release
pipeline, and docs/xla.md covers the XLA PJRT fork, which is pinned outside
migration.toml entirely.
In local mode, ask before pushing fork branches, opening the PR, or filing an issue. The required end-to-end test needs no extra confirmation.
Read the Descriptor
Read the target fork's section in config/external/migration.toml. It gives:
upstream— the repo we rebase onto. Every fork has one.group— if present, refresh every section in the group together in one PR (read them all now); if absent, this pin refreshes alone.base_select(+derived_from) — how to choose the new upstream base.pin— where the resolved pin is recorded (isolated_projectuv.lock,descriptor:<path>#<section>SHA, orrelease:<path>prebuilt wheel); drives the re-pin step.branch— the fork branch this pin tracks (mainfor a single-pin fork and for the vllm GPU pin;tpufor the vllm fork's TPU pin). The refresh stages on<branch>-next; an admin promotes that validated tip after reviewing the draft Marin PR.e2e— the Marin end-to-end that validates the refresh.blocker_assignee— who owns the "can't migrate" issue.nuances— constraints a human must respect (torch pins, known-good ceilings).
The descriptor records how to migrate; the pin source it names holds the actual revision.
Outcome
- If no newer base is selected and no pin metadata needs repair, exit successfully with a no-op summary.
- On success, create the rollback and date tags described in
docs/promotion-protocol.md, then open exactly one draft PR inmarin-community/marinfor the fork or group after the e2e passes. A grouped refresh re-pins every group section at its staged tip in that single PR. State the exact<branch>-nextto<branch>admin promotion still required, request the descriptor'sblocker_assigneeas reviewer, and monitor the PR per.agents/skills/commit/SKILL.md. - On an unresolved blocker, do not open a PR. Create or update one
marin-community/marinissue assigned toblocker_assignee, titledFork refresh blocked: <fork> — <short reason>, with current pins, the selected base, branch names/SHAs if created, attempted fixes, the remaining failure, and artifacts.
What ships with it
4 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 Changed · -50 lines 2404546fefe5
- 5d ago First seen · 335 lines · 27 tokens per session scan A 650f9f6996b4
refresh-fork is a skill published in the GitHub repository marin-community/marin (3,354 stars, last pushed yesterday), licensed Apache-2.0. It adds 27 tokens to every session and 4,074 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…