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/archive-experimentsnpx skills add marin-community/marin --skill archive-experimentsgit 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/archive-experiments)<a href="https://agentmods.dev/skills/marin-community/marin/archive-experiments"><img src="https://agentmods.dev/badge/skills/marin-community/marin/archive-experiments.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.1 | $0.00021 | $0.00797 |
| Opus 5 | $0.00010 | $0.00398 |
| Sonnet 5 | $0.00004 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
archive-experiments 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 6d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Archive Legacy Experiments
Overview
Retire old experiment scripts without losing their history: put the code behind a dated archive tag and leave a canonical comment on the originating GitHub issues so future readers can find the last snapshot.
Prerequisites
- Local checkout of
marinwith push access toorigin. ghCLI installed and authenticated formarin-community/marin.- List of experiment issues and their corresponding filenames under
experiments/. - The PR number for the cleanup you are referencing; if the directing human has not given one, ask them before posting anything.
Guidelines for Humans
1. Snapshot the experiments behind an archive tag
- Identify the commit that should house the archived experiments (usually
mainafter the cleanup). Record it withgit rev-parse HEAD. - Pick a date-based tag name in the form
archive/YYYYMMDD. - Create and push the tag:
TAG=archive/20251114 git tag "${TAG}" <commit-sha> git push origin "${TAG}" - If an older tag (e.g.,
exp_cleaning/YYYYMMDD) described the same snapshot, delete it locally and remotely so only thearchive/tag remains.
2. Post the canonical archive comment on each issue
- Confirm the cleanup PR number (
PR_NUM); if nobody has provided one yet, ping the human operator for it before continuing. - For every experiment issue, build the file URL:
https://github.com/marin-community/marin/tree/${TAG}/experiments/<filename>. - Use the standardized note below, swapping in the filename-specific URL and PR reference:
This experiment has been archived to reduce clutter and preserve velocity (see PR #<PR_NUM>). It is last available in the `archive/YYYYMMDD` tag at <URL>. Please open an issue if you need help unarchiving it. - Post the comment with
gh issue comment:ISSUE=102 FILE=exp102_classifier_ablations.py PR_NUM=1999 URL="https://github.com/marin-community/marin/tree/${TAG}/experiments/${FILE}" gh issue comment "${ISSUE}" \ --body "This experiment has been archived to reduce clutter and preserve velocity (see PR #${PR_NUM}). It is last available in the \`${TAG}\` tag at ${URL}. Please open an issue if you need help unarchiving it." - Confirm the comment renders correctly (PR reference should auto-link and the URL should jump straight to the file in the archive tag).
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.
- 6d ago First seen · 64 lines · 21 tokens per session scan A f33d10b328eb
archive-experiments is a skill published in the GitHub repository marin-community/marin (3,440 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 797 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
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…