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 jcarlosrodicio/opencode-agent-orchestration-kit --skill oak-update-docsgit clone --depth 1 https://github.com/jcarlosrodicio/opencode-agent-orchestration-kitWrote 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/jcarlosrodicio/opencode-agent-orchestration-kit/oak-update-docs)<a href="https://agentmods.dev/skills/jcarlosrodicio/opencode-agent-orchestration-kit/oak-update-docs"><img src="https://agentmods.dev/badge/skills/jcarlosrodicio/opencode-agent-orchestration-kit/oak-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/jcarlosrodicio/opencode-agent-orchestration-kit/oak-update-docs"><img src="https://agentmods.dev/badge/skills/jcarlosrodicio/opencode-agent-orchestration-kit/oak-update-docs.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.00052 | $0.00407 |
| Opus 5.5 | $0.00021 | $0.00163 |
| Sonnet 5.5 | $0.00010 | $0.00081 |
| Haiku 4.5 | $0.00005 | $0.00041 |
Grade A, and why
oak-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 17d 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
Update Docs
Overview
The next session, human or agent, starts from the documentation. A change that leaves it stale costs more later than it saves now. Updating the owning docs is part of the change, not a follow-up, and it happens before delivery.
Map each change to its owning doc
| The change touched | Update |
|---|---|
| an API contract | the API document |
| a schema, migration or model | the data-model document |
| a module or service boundary | the architecture document, plus an ADR if a rule was bent |
| a new command, script or environment variable | the setup guide |
| behavior a reader would not expect | the spec, or an ADR |
| a roadmap item it completes | the roadmap entry and its status |
The roadmap entry is the update most often forgotten. Check it every time.
How to write the update
- Match the structure the document already has.
- Explain intent and constraints. Do not paraphrase the code.
- Fix every statement the change made false, not just the paragraph you were looking for.
- Do not create a new document when one already owns the topic.
- Do not add a changelog entry unless the project keeps a changelog.
- Do not leave a TODO in place of the update.
Report
End with one of:
- the list of documents updated; or
- the documents you checked, and why each was unaffected.
"No docs needed" without that list is not a report.
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.
- 17d ago First seen · 55 lines · 52 tokens per session scan A e3009acee92b
oak-update-docs is a skill published in the GitHub repository jcarlosrodicio/opencode-agent-orchestration-kit (133 stars, last pushed 18d ago), licensed Apache-2.0. It adds 52 tokens to every session and 407 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-09-29.
Other skills, from other repositories
qa
Run scalable, isolated live QA for nac development. The top-level local orchestrator must parse n (default 4), dispatch one setup worker with this skill, copy its n assignment contracts verbatim into exactly n parallel test workers with this skill, then dispatch one aggregate worker with this skill using all test…
release
Cut and publish a full stable NAC release after main, release-PR, and publication CI pass. Use when a maintainer asks for a stable version bump, tag, or GitHub Release. Never use for release candidates; NAC RC releases are automated.
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
ahk-test
Design, write, and run behavior-focused tests for an objective or existing code. Writes test files only and reports evidence. No tasks created, no harness tracking.
ahk-review
Preview a code review against ticket/objective alignment, with deep semantic (name-vs-behavior) analysis. No tasks created, no harness tracking.
ahk-consultant
Get technical advice or review on an approach, idea, or change. References available skills for best practices. No tasks created, no harness tracking.