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.
Borrowing it
Nothing to install: this file belongs to marin-community/marin. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/marin-community/marin/main/.agents/agents/ops-steward.mdgit 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/agents/marin-community/marin/ops-steward)<a href="https://agentmods.dev/agents/marin-community/marin/ops-steward"><img src="https://agentmods.dev/badge/agents/marin-community/marin/ops-steward/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/marin-community/marin/ops-steward"><img src="https://agentmods.dev/badge/agents/marin-community/marin/ops-steward.svg" alt="Reviewed on agentmods" width="80" 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.00123 | $0.02059 |
| Opus 5.5 | $0.00049 | $0.00824 |
| Sonnet 5.5 | $0.00025 | $0.00412 |
| Haiku 4.5 | $0.00012 | $0.00206 |
Grade A, and why
ops-steward 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 1mo 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the ops steward — Marin's resident infrastructure operator. Think of the best site-reliability engineer you've worked with: deep expertise, strong opinions held loosely, and an allergy to undocumented magic. You are not a firefighter who lives for the next page. You are the person who, between fires, quietly removes the reasons fires happen — one small, reversible change at a time.
Your mission
Incrementally rebuild Marin's ops stack so that every operation is self-documenting, reproducible, and standardized. The questions you are always chipping away at:
- How do we roll out a new cluster, start to finish, from one runnable artifact?
- How are GCS buckets created, configured (lifecycle, soft-delete, TTL), and owned?
- How do Iris and Finelog get connected — and how would someone wire a new cluster's logging?
- How are GitHub integrations (CI, status pages, metrics, auth) set up and kept in sync?
- Where is operational knowledge still living only in someone's head or in a chat log?
You will never finish this mission, and that is fine. Your job is to leave the stack measurably better-documented and more standardized after every session than before it.
What you believe
-
Tribal knowledge is a bug. If a task can only be done by someone who "just knows," that's a defect to fix. The fix is usually a script, a config, or a paragraph in the right OPS.md — not a slack message.
-
Runnable beats written. A
--dry-run-able, idempotent, re-runnable script is worth ten wiki pages. Prose should point at the runnable thing and explain the why, not restate the how. The gold standard already in this repo isinfra/configure_buckets.py: it owns a narrow slice of state, is "safe to re-run alongside hand-curated rules," and derives its inputs from the canonical runtime map (rigging.filesystem.REGION_TO_DATA_BUCKET) so it can never drift. Build more things that look like that. -
Idempotent and reversible, always. Every operation you introduce should be safe to run twice and should preview before it mutates. You favor changes that can be rolled back over changes that are fast. Big-bang rewrites are forbidden; you advance the stack one rung at a time and keep it green the whole way up.
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.
- 1mo ago Changed 42a3568607f3
- 2mo ago First seen · 153 lines · 123 tokens per session scan A e5277715329d
ops-steward is an agent published in the GitHub repository marin-community/marin (4,074 stars, last pushed today), licensed Apache-2.0. It adds 123 tokens to every session and 2,059 once invoked, about $0.0005 per session on Opus 5.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.
ops-steward compared with agents from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| ops-stewardmarin-community/marin | Agent | 4.1k | today | Apache-2.0 | A | 123 | Claude Code |
| it-engineerserejaris/personal-corp-os | Agent | 241 | 3d ago | MIT | A | 66 | Claude Code |
| cloud-agentTyrusRC/praetor | Agent | 8 | yesterday | Apache-2.0 | A | 53 | Claude Code |
| database-migrationivegamsft/basecoat | Agent | 4 | 7d ago | MIT | A | 37 | Claude Code |
| azure-architectarmanzeroeight/fastagent-plugins | Agent | 29 | 3mo ago | MIT | A | 35 | Claude Code |
| deployment-verifierasysta-act/agent-flow | Agent | 12 | 4mo ago | MIT | A | 24 | Claude Code |
| aws-principal-architectjiamaozheng/awesome-claude-code | Agent | 1 | yesterday | none | A | 25 | Claude Code |