codehub-document

A documentation tool for creating a linked set of Markdown files that explains a codebase, its architecture, and its modules.

In plain words
What is it for?
Use it to generate or refresh repository documentation, architecture books, module maps, and documentation for groups of repositories.
Why use it?
It turns an indexed repository into a structured reference, so developers do not have to piece the system together manually.

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/theagenticguy/opencodehub/codehub-document
Any agent
npx skills add theagenticguy/opencodehub --skill codehub-document
Clone the repo
git clone --depth 1 https://github.com/theagenticguy/opencodehub

Made for: Claude Code, Codex.

Per session 159 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,176 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.00159 $0.03176
Opus 5 $0.00079 $0.01588
Sonnet 5 $0.00032 $0.00635
Haiku 4.5 $0.00016 $0.00318

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

Security

Grade A, and why

codehub-document 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.

.claude/skills/codehub-document/SKILL.md · 153 lines

How it starts

The opening of the file, as written. The whole thing — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.

codehub-document

Primary artifact generator. Produces a tree of cross-linked Markdown under .codehub/docs/ (single-repo) or .codehub/groups/<name>/docs/ (group mode) using a three-phase orchestration: Phase 0 parallel precompute wavesPhase 1 file-level subagent fan-out (one packet = one output file) → Phase 2 deterministic cross-reference assembly.

Model policy. This skill runs on Sonnet by default. Bump to Opus in two cases:

  1. --refresh --group combined — the pruning + partial fan-out across members needs the extra judgment.
  2. Any individual packet may set model: opus in its frontmatter to opt into Opus for synthesis-heavy roles. The cross-repo skeletons (doc-cross-repo-*) and doc-analysis-risk-hotspots typically do this; full-scan single-repo packets stay on Sonnet.

Preconditions (check before Phase 0)

  1. mcp__codehub__list_repos returns the target. If not, emit Run codehub analyze first — repo <name> is not indexed. and stop.
  2. codehub status reports fresh. If stale, emit Run 'codehub analyze' first — index is stale and stop.
  3. Group mode only: mcp__codehub__group_status({group}) must return fresh: true for every member. If any member is stale, abort and name each stale repo.

Arguments

  • [output-dir] (optional positional) — where to write. Default is .codehub/docs/ (gitignored). With --committed, default flips to docs/codehub/ and the skill does not add a .gitignore entry.
  • --group <name> — enable group mode. Phase 0 calls group_list + group_status + group_contracts + group_query. Phase CD dispatches doc-cross-repo.
  • --committed — write under docs/codehub/ (or user-supplied path) instead of .codehub/docs/. Does not touch .gitignore.
  • --refresh — consult .docmeta.json, identify stale sections by comparing max(mtime(section.sources[])) against section.mtime, and dispatch exactly one file-level subagent per stale section (re-seeding its packet from templates/agents/<role>.md). Phase 2 always re-runs.
  • --section <name> — regenerate one named section (e.g., architecture/system-overview). Dispatches exactly one subagent with one skeleton and re-runs Phase 2. Useful for targeted updates.

Read the full file on GitHub · 153 lines

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 · 153 lines · 159 tokens per session scan A a1b92eda30eb

Subscribe to this mod's changes

codehub-document is a skill published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 20d ago), licensed Apache-2.0. It adds 159 tokens to every session and 3,176 once invoked, about $0.0008 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

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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…

openai/codex · 114 tokens

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…

openai/codex · 113 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 170 tokens