doc-architecture-system-overview

A guide to the project's state machines, with one Mermaid diagram for each. A state machine describes the states something can be in and the events that move it between states.

In plain words
What is it for?
Use it to document declared states, allowed transitions, and where each state machine is defined.
Why use it?
It makes lifecycle rules easier to understand than scattered conditional logic or declarations in source code.

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-system-overview
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,325 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.01325
Opus 5 $0.00000 $0.00662
Sonnet 5 $0.00000 $0.00265
Haiku 4.5 $0.00000 $0.00133

Measured 2d ago against content hash a59b1b63f9ec, 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-system-overview 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 2d 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.

.claude/skills/codehub-document/templates/agents/doc-architecture-system-overview.md · 101 lines

How it starts

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

Packet · {{ repo }} · architecture/system-overview.md

1. Objective

Produce {{ docs_root }}/architecture/system-overview.md: a 400–600-word narrative of what {{ repo }} does and how its top-level pieces fit, with one stack table and one Mermaid flowchart LR of the top 6 modules.

2. Scope

  • Create: {{ docs_root }}/architecture/system-overview.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
Project profile {{ context_path }} § Repo profile cached
Top communities {{ context_path }} § Top communities cached
Top processes {{ context_path }} § Top processes cached
External deps {{ context_path }} § Stack or mcp__codehub__dependencies({repo: "{{ repo }}"}) cached if digest present
Module relations mcp__codehub__context({symbol: <community-name>}) per top 6 modules mid-run

4. Process

  1. Read {{ context_path }} and Read {{ prefetch_path }}. Confirm {{ repo }} profile, top-6 community names, top processes.
  2. For each of the top 6 communities (from .context.md § Top communities): call mcp__codehub__context({symbol: <community-name>}) to pull inbound/outbound relation counts. Cache the summary in this packet's Work log.
  3. Pull the external dependencies list from .context.md § Stack (or call dependencies if not cached). Keep the top 15 by usage.
  4. Resolve the stack layers by inspecting project_profile.entry_points and cross-referencing the top communities with their file_path prefixes.
  5. Draft the narrative (400–600 words). Structure: paragraph 1 = what the repo does, paragraph 2 = how the pieces fit.
  6. Draft the Stack table with columns Layer | Technology | Source. Every row cites path:LOC.
  7. Draft the Module-map Mermaid flowchart LR — ≤ 20 nodes, short labels (≤ 20 chars), edges from relation counts ≥ 1.
  8. Write {{ docs_root }}/architecture/system-overview.md with H1 = {{ repo }} · System overview.

Read the full file on GitHub · 101 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. 2d ago First seen · 101 lines · 0 tokens per session scan A a59b1b63f9ec

Subscribe to this mod's changes

doc-architecture-system-overview is an agent published in the GitHub repository theagenticguy/opencodehub (3 stars, last pushed 21d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,325 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.