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/commitnpx skills add marin-community/marin --skill commitgit clone --depth 1 https://github.com/marin-community/marinWhat 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.00028 | $0.02061 |
| Opus 5 | $0.00014 | $0.01030 |
| Sonnet 5 | $0.00006 | $0.00412 |
| Haiku 4.5 | $0.00003 | $0.00206 |
Grade A, and why
commit 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit and PR
Before authoring a commit or PR title or body, read:
.agents/skills/writing-style/SKILL.md.agents/skills/writing-style/pull-requests.md.agents/skills/writing-style/ai-writing-donts.md
Clean and validate the diff, commit it, run the advisory review over the committed branch, push, update the PR, then monitor it. A WIP checkpoint may stop after clean-up, lint, staging, commit, and push.
1. Clean up your own diff
Read the complete branch diff and remove dead code, weak tests, stale prose, debugging artifacts, and unrelated changes.
If the diff touches tests and this commit is intended for a PR or review, read
root TESTING.md and the relevant module-specific AGENTS.md or testing docs
as part of this self-review. Apply TESTING.md's behavioral-value gate to every
changed test. Delete disposable probes and low-value tests before a PR-ready
commit.
2. Lint and format
./infra/pre-commit.py --changed-files --fix # diff-scoped; use --all-files for a full sweep
This is the required entry point; do not substitute uv run pre-commit, skip
hooks, or weaken checks.
3. Tests and docs checks (when relevant)
uv run --no-project infra/ci/run_tests.pyto run affected safe unit tests. Do not override the repository's default marker expression.- If docs pages were added/deleted/renamed:
uv run python infra/check_docs_source_links.py. - If the change is docs-heavy:
uv run mkdocs build --strict.
4. Stage changes
Review git status and git diff, then stage only this task's explicit files.
Never stage secrets or unrelated work.
5. Commit
Follow writing-style/pull-requests.md for the commit subject and body.
Review the exact message before committing. After the commit, inspect it with
git show -s --format='%s%n%n%b' HEAD; do not push if a tool added attribution,
a session trailer, or other text that was not in the reviewed message.
If a hook fails, fix the issue and create a new commit. Do not amend unless the user asks.
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 · 200 lines · 28 tokens per session scan A 43a8a81ba033
commit is a skill published in the GitHub repository marin-community/marin (3,039 stars, last pushed 2d ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,061 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.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…