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 skills add DasDigitaleMomentum/opencode-processing-skills --skill update-docsgit clone --depth 1 https://github.com/DasDigitaleMomentum/opencode-processing-skillsWrote 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/dasdigitalemomentum/opencode-processing-skills/update-docs)<a href="https://agentmods.dev/skills/dasdigitalemomentum/opencode-processing-skills/update-docs"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/update-docs/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/skills/dasdigitalemomentum/opencode-processing-skills/update-docs"><img src="https://agentmods.dev/badge/skills/dasdigitalemomentum/opencode-processing-skills/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00050 | $0.01276 |
| Opus 5.5 | $0.00020 | $0.00510 |
| Sonnet 5.5 | $0.00010 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00128 |
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 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Update Documentation
What This Skill Does
Updates existing project documentation to reflect code changes. Handles:
- Detecting which documentation is affected by recent changes
- Updating module documentation (symbols, structure, data flow)
- Updating feature documentation (new behavior, changed flows)
- Updating the project overview (new modules, changed architecture)
- Ensuring cross-references remain valid
When to Use
- After implementing a feature or fixing a bug that changes behavior
- After refactoring that affects module structure or symbols
- When the user says documentation is "outdated" or asks to "update docs"
- After a plan phase is completed and code has changed
Do NOT use this skill to create documentation from scratch - use generate-docs instead.
Execution Model
- The primary agent spawns
doc-explorer.doc-explorermaps code changes to docs and updates files underdocs/. - Rationale: doc updates are grounded in repo state; exploration + edits belong together to avoid losing "why this section changed".
- For large change sets affecting multiple modules,
doc-explorerself-delegates per module (see Self-Delegation below). - The primary agent should keep chat output minimal (what docs changed + any gaps).
Self-Delegation
When changes span multiple modules, doc-explorer SHOULD delegate per-module updates to separate doc-explorer instances via the Task tool:
- Orchestrator instance: Identifies affected modules from git diff, spawns per-module instances
- Per-module instance: Receives scoped task ("update docs for module X, changes: ..."), reads existing doc, updates it
- Orchestrator: Updates cross-cutting artifacts (overview, feature docs), validates cross-references
This prevents token bloat from accumulating analysis of all changed modules in a single context.
Workflow
Step 1: Identify What Changed
Determine the scope of changes using one or more methods:
If changes are recent (current session):
- Review the files modified in the current session
- Check git diff for uncommitted changes
What ships with it
3 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.
- 1mo ago First seen · 142 lines · 50 tokens per session scan A a3a6cc9352ac
update-docs is a skill published in the GitHub repository DasDigitaleMomentum/opencode-processing-skills (60 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,276 once invoked, about $0.0002 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.
Other skills, from other repositories
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan, then execute, a migration of a project from the mem0 open-source / self-hosted SDK (local Memory class) to the mem0 Platform / hosted SDK (MemoryClient). TRIGGER when: the developer wants to move, switch, or migrate mem0 off OSS/self-hosted to the hosted API, e.g. "migrate my mem0 setup to the platform", "switch…
safe-refactor
Restructure code while preserving behavior. Use for extraction, consolidation, ownership moves, or cleanup where verification must bracket structural edits.