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 agentmods add agents/theagenticguy/opencodehub/doc-diagrams-componentsgit clone --depth 1 https://github.com/theagenticguy/opencodehubWhat 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 | $0.00000 | $0.01386 |
| Opus 5 | $0.00000 | $0.00693 |
| Sonnet 5 | $0.00000 | $0.00277 |
| Haiku 4.5 | $0.00000 | $0.00139 |
Grade A, and why
doc-diagrams-components 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packet · {{ repo }} · diagrams/architecture/components.md
1. Objective
Produce {{ docs_root }}/diagrams/architecture/components.md: a single Mermaid classDiagram of the top 8 components of {{ repo }} with HAS-A / USES edges, capped at 20 total nodes.
2. Scope
- Create:
{{ docs_root }}/diagrams/architecture/components.md - Do not touch: any other file under
{{ docs_root }}/, any source file in the repo,.context.md,.prefetch.md, or any.packets/*.mdother 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 relations | {{ prefetch_path }} § sql relations or mcp__codehub__sql({query: "SELECT src, dst, type FROM edges WHERE type IN ('CONTAINS','CALLS','IMPORTS') LIMIT 500"}) |
cached if digest present; mid-run otherwise |
| Component method list | mcp__codehub__context({symbol: <community-name>}) per top 8 |
mid-run |
4. Process
Read {{ context_path }}andRead {{ prefetch_path }}. Confirm top-8 community names and their file-path roots.- Pull the raw edge set from
.prefetch.md § sql relations(kindsCONTAINS,CALLS,IMPORTS). If not cached, callmcp__codehub__sqlwith the query above and cache the digest in this packet's Work log. - Project file-level edges down to the community level: collapse every
(source_community, target_community, kind)triple into a single edge, labeled with a one-word verb (contains,invokes,imports,depends). - For each of the top 8 communities, call
mcp__codehub__context({symbol: <community-name>})and select the top 3-5 outbound method names by call count. These populate theclassDiagrammethod list for that class. - If the projected graph has > 20 nodes, keep the top-20 by edge count and move the overflow into a
## Legend (overflow)table with columnsNode | Edges | Reason for elision. - Draft the Mermaid
classDiagram. Max 8 classes; each class has 3-5 methods; relationships labeled with one-word verbs. Write {{ docs_root }}/diagrams/architecture/components.mdwith H1 ={{ repo }} · Component view.
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.
- yesterday First seen · 100 lines · 0 tokens per session scan A b19e8fa8c6f2
doc-diagrams-components 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,386 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.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.