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/update-docsnpx skills add marin-community/marin --skill update-docsgit 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/update-docs)<a href="https://agentmods.dev/skills/marin-community/marin/update-docs"><img src="https://agentmods.dev/badge/skills/marin-community/marin/update-docs.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.00032 | $0.00298 |
| Opus 5 | $0.00016 | $0.00149 |
| Sonnet 5 | $0.00006 | $0.00060 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
update-docs 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 4d 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.
What it actually says
Skill: Update Docs
Use this when a task changes behavior, reveals stale instructions, creates a new operational pattern, or produces guidance that should survive outside the issue thread.
What to Update
- User-facing docs when behavior or configuration changes.
- Operational docs when commands, service setup, dashboards, alerts, or recovery procedures change.
- Skill docs when an agent workflow becomes reusable.
- Experiment reports or indexes when the work produces durable research findings.
Prefer editing the nearest existing doc over adding a new one. Add a new doc only when the topic lacks a natural home or would make an existing page unfocused.
Content Rules
- Describe current behavior, not aspiration.
- Include exact commands and paths for operational procedures.
- Remove or correct stale instructions rather than adding caveats around them.
- Keep broad docs concise; put detailed run notes in logbooks or issue comments.
Done Criteria
- Docs and code agree for the changed behavior.
- The next agent or human can find the authoritative procedure without reading the whole issue thread.
- Any generated guidance is generalized enough to reuse and specific enough to act on.
Related Skills
Follow .agents/skills/writing-style/SKILL.md for writing-style guidance.
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.
- 4d ago First seen · 43 lines · 32 tokens per session scan A 7f7c4ced7659
update-docs is a skill published in the GitHub repository marin-community/marin (3,354 stars, last pushed today), licensed Apache-2.0. It adds 32 tokens to every session and 298 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…