doc-cross-repo-portfolio-map

doc-cross-repo-portfolio-map is an agent for Claude Code from theagenticguy/opencodehub. It costs 0 tokens per session (1,782 once invoked), scanned A, original, Apache-2.0.

A documentation task that describes the structure of a group of software repositories. It creates a written overview, a left-to-right Mermaid diagram, and links to each repository's documentation.

In plain words
What is it for?
Use it to document member repositories, their contract counts, the group's overall shape, and the location of each repository's detailed docs.
Why use it?
It gives developers a shared map of a multi-repository codebase. A multi-repository group is a collection of separate codebases that work together.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions subagents.

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

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for doc-cross-repo-portfolio-map

README.md
[![agentmods](https://agentmods.dev/badge/agents/theagenticguy/opencodehub/doc-cross-repo-portfolio-map.svg)](https://agentmods.dev/agents/theagenticguy/opencodehub/doc-cross-repo-portfolio-map)
Your own site
<a href="https://agentmods.dev/agents/theagenticguy/opencodehub/doc-cross-repo-portfolio-map"><img src="https://agentmods.dev/badge/agents/theagenticguy/opencodehub/doc-cross-repo-portfolio-map.svg" alt="Measured on agentmods" height="20"></a>
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,782 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.1 $0.00000 $0.01782
Opus 5 $0.00000 $0.00891
Sonnet 5 $0.00000 $0.00356
Haiku 4.5 $0.00000 $0.00178

Measured 5d ago against content hash 5b021b274d1f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

doc-cross-repo-portfolio-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 5d 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-cross-repo-portfolio-map.md · 107 lines

How it starts

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

Packet · {{ group }} · cross-repo/portfolio-map.md

Group mode only. This packet runs when the skill orchestrator is invoked with --group {{ group }}. In single-repo mode it is never seeded.

1. Objective

Produce {{ group_docs_root }}/cross-repo/portfolio-map.md: a 2-paragraph narrative of the {{ group }} group's shape, a Mermaid flowchart LR of its member repos with contract-count edges, and a ## Repos section with per-member H2 + relative link into each member's own .codehub/docs/ tree.

2. Scope

  • Create: {{ group_docs_root }}/cross-repo/portfolio-map.md
  • Do not touch: any other file under {{ group_docs_root }}/, any file under a member repo (including {{ member_repos }}/.codehub/docs/), {{ group_context_path }}, {{ group_prefetch_path }}, or any .packets/*.md other than this one.

3. Input specification

Source Read how Cache state
Group shared context Read {{ group_context_path }} always first
Group prefetch ledger Read {{ group_prefetch_path }} always first
Member list + freshness {{ group_context_path }} § Members / {{ group_prefetch_path }} § group_list,group_status cached
Group contracts {{ group_prefetch_path }} § group_contracts cached
Per-member one-line description {{ group_context_path }} § Member profiles cached
Member docs-root paths derived: ../{{ member_repos[i] }}/.codehub/docs/README.md n/a

4. Process

  1. Read {{ group_context_path }} and Read {{ group_prefetch_path }}. Confirm the member list under § Members and re-verify that every member is tagged fresh in the cached group_status digest. If any member is stale, abort and write the gap to Work log — the orchestrator's Phase 0 gate should have caught this.
  2. Pull the contract inventory from {{ group_prefetch_path }} § group_contracts. Aggregate by (producer_repo, consumer_repo) into an edge-count table.
  3. Pull one-line domain descriptions for each member from {{ group_context_path }} § Member profiles. These become the second line of each node label via <br/>.
  4. Draft the 2-paragraph narrative: paragraph 1 = what the group does as a whole (domain, scope); paragraph 2 = how the members relate (who produces for whom, which member is the hub). Every factual claim carries a repo:path:LOC citation.
  5. Draft the Mermaid flowchart LR: one node per member repo with the two-line label "<repo><br/><one-line domain>"; one edge per (producer, consumer) pair labeled contracts: N. Cap at 20 nodes — if the group has > 20 members, keep the top-20 by inbound+outbound contract count and move the overflow to a ## Legend (overflow) table.
  6. Draft the ## Repos section: one H2 per member (## <repo> — <one-line description>), each with 1-2 repo:path:LOC citations and a [See {{ member_repos[i] }} docs →](../{{ member_repos[i] }}/.codehub/docs/README.md) link.
  7. Write {{ group_docs_root }}/cross-repo/portfolio-map.md with H1 = {{ group }} · Portfolio map.

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

Subscribe to this mod's changes

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