oad/docs

An EvoFlux workflow for updating project documentation after code changes. It keeps the related documents short, aligned with the implementation, and free of unnecessary duplication.

In plain words
What is it for?
Use it after changing code to update the relevant documentation and link to existing information where appropriate.
Why use it?
It reduces the risk that documentation becomes outdated or repeats information already present in the code.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/evoelsewhere/evoflux/docs
Any agent
npx skills add evoelsewhere/evoflux --skill docs
Clone the repo
git clone --depth 1 https://github.com/evoelsewhere/evoflux

Made for: Claude Code, Codex.

Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 77 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00016 $0.00077
Opus 5 $0.00008 $0.00039
Sonnet 5 $0.00003 $0.00015
Haiku 4.5 $0.00002 $0.00008

Measured yesterday against content hash 35dfcd28217a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

oad/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 yesterday.

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.

.evoflux/skills/oad/docs/SKILL.md · 9 lines

What it actually says

Update related documents according to the changes made in the codebase. Make sure the docs are not duplicated and including the code itself. If the relevant documents exist, update them with the new changes and/or refer to it.

Keep it short, simple and concise (if possible)

Changes

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.

  1. yesterday First seen · 9 lines · 16 tokens per session scan A 35dfcd28217a

Subscribe to this mod's changes

oad/docs is a skill published in the GitHub repository evoelsewhere/evoflux (5 stars, last pushed 5d ago), licensed Apache-2.0. It adds 16 tokens to every session and 77 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-31.

Related

Other skills, from other repositories

kane-cli

Browser automation + AI test authoring via kane-cli - run browser objectives, generate & refine test scenarios/cases from a description, design requirement-linked test suites from a PRD/spec (assurance), parse NDJSON output, inspect logs, save runnable test.md. Use for any task requiring a real browser (navigate…

LambdaTest/kane-cli · 159 tokens

control-chrome

Control the user's Chrome browser for tasks that depend on existing Chrome state: tabs, logged-in sessions, or extensions. Prefer purpose-built connectors, APIs, or CLIs when available.

rojim666/SztuCode · 40 tokens

recent-release

Render Rove's recent releases as a self-contained, Rove-styled HTML page (Chinese by default). Reads shipped notes from packages/kobe/CHANGELOG.md + git tags, filters to user-facing changes, and emits one standalone .html file in the claude theme (terracotta on near-black, JetBrains Mono, terminal chrome). Use when…

Sma1lboy/rove · 112 tokens

yutori-scout

Set up continuous web monitoring with Yutori Scouts. Use when the user wants to track news, competitors, product updates, funding rounds, price changes, or any recurring web information.

yutori-ai/yutori-mcp · 43 tokens

yutori-computer-use

Run local Mac desktop tasks with Yutori computer use. Use when the user wants to operate macOS apps, websites in a local browser, or cross-app workflows on the visible desktop.

yutori-ai/yutori-mcp · 45 tokens

plan-review-triggers

Required reading whenever drafting any multi-step proposal, implementation plan, refactor approach, or response containing file paths and decision points. Use BEFORE writing any response that lists 3+ file paths, 2+ option-tradeoffs, a "Plan:"/"Steps:"/"Concrete changes:" section, or ends with "OK to proceed?" /…

ndom91/open-plan-annotator · 199 tokens