doc-architecture-module-map

A documentation task that creates a map of the main modules in a code repository. Each module gets a short description and a list of up to eight important files with their paths and line counts.

In plain words
What is it for?
Use it to create docs/architecture/module-map.md as a high-level guide to repository modules and their files.
Why use it?
It gives developers a structured starting point for understanding the repository's layout and the files that matter most in each module.

Agent for Claude Code

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 agents/theagenticguy/opencodehub/doc-architecture-module-map
Clone the repo
git clone --depth 1 https://github.com/theagenticguy/opencodehub

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,509 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.00000 $0.01509
Opus 5 $0.00000 $0.00754
Sonnet 5 $0.00000 $0.00302
Haiku 4.5 $0.00000 $0.00151

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

Security

Grade A, and why

doc-architecture-module-map 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/templates/agents/doc-architecture-module-map.md · 103 lines

How it starts

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

Packet · {{ repo }} · architecture/module-map.md

1. Objective

Produce {{ docs_root }}/architecture/module-map.md: one H2 per top module, each with a one-paragraph description and a bullet list of the module's top 8 files cited as `path:LOC` with (N LOC) suffix.

2. Scope

  • Create: {{ docs_root }}/architecture/module-map.md
  • Do not touch: any other file under {{ docs_root }}/, any source file in the repo, .context.md, .prefetch.md, or any .packets/*.md other than this one.

3. Input specification

Source Read how Cache state
Shared context Read {{ context_path }} always first
Prefetch ledger Read {{ prefetch_path }} always first
Top communities {{ context_path }} § Top communities cached
Community member files {{ prefetch_path }} § community members or mcp__codehub__sql({query: "SELECT name, file_path, start_line FROM nodes WHERE kind='File' AND community_id = <id> ORDER BY file_path"}) cached if digest present
Community relations mcp__codehub__context({symbol: <community-name>}) per module mid-run (only if cache miss)
File LOC Read <file> then count lines mid-run

4. Process

  1. Read {{ context_path }} and Read {{ prefetch_path }}. Confirm {{ repo }} profile and the ordered list of top communities.
  2. For each of the top 8 communities, pull the member file list from .prefetch.md § community members. If absent, call sql({query: "SELECT name, file_path, start_line FROM nodes WHERE kind='File' AND community_id = <id> ORDER BY file_path LIMIT 50"}) and cache the digest in this packet's Work log.
  3. For each module, rank files by semantic weight (inbound relation count from cached context digest if present, else alphabetical fallback). Keep the top 8.
  4. For every file in the shortlist, Read it to compute LOC. Record path:LOC + total line count per file in the packet Work log.
  5. Draft the one-paragraph description per module. Anchor the paragraph on the module's inferred_label and its highest-weight file, each cited `path:LOC`.
  6. Collapse any module with fewer than 3 files into a trailing ## Supporting code H2 that lists those files as flat bullets.
  7. Write {{ docs_root }}/architecture/module-map.md with H1 = {{ repo }} · Module map and one H2 per module in top-community order.

Read the full file on GitHub · 103 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 · 103 lines · 0 tokens per session scan A b73a8f7a0e03

Subscribe to this mod's changes

doc-architecture-module-map is an agent published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 20d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,509 tokens. 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 agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

playwright-test-generator

Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

AVM Owner Triage

Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.

github/awesome-copilot · 61 tokens

Ultimate Transparent Thinking Beast Mode

Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.

github/awesome-copilot · 11 tokens

code-reviewer

Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.

anthropics/claude-cookbooks · 52 tokens