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-analysis-ownershipgit 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.01446 |
| Opus 5 | $0.00000 | $0.00723 |
| Sonnet 5 | $0.00000 | $0.00289 |
| Haiku 4.5 | $0.00000 | $0.00145 |
Grade A, and why
doc-analysis-ownership 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Packet · {{ repo }} · analysis/ownership.md
1. Objective
Produce {{ docs_root }}/analysis/ownership.md: a ranked table of folders in {{ repo }} by top-contributor share, followed by a ## Single points of failure H2 listing paths where the top owner holds > 70% of commits — each SPOF row gets a one-sentence mitigation suggestion.
2. Scope
- Create:
{{ docs_root }}/analysis/ownership.md - Do not touch:
{{ docs_root }}/analysis/risk-hotspots.md,{{ docs_root }}/analysis/dead-code.md, 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 |
| Owners summary | {{ context_path }} § Owners summary |
cached |
| Owners per folder | {{ prefetch_path }} § owners or mcp__codehub__owners({path: <folder>}) |
cached when present |
| Folder roster | mcp__codehub__sql({query: "SELECT DISTINCT file_path FROM nodes WHERE kind='File'"}) + folder-prefix grouping |
mid-run, only if .context.md roster is truncated |
| Top-contributor share | owners response field share |
cached or mid-run |
4. Process
Read {{ context_path }}andRead {{ prefetch_path }}. Confirm Owners summary and cached owners digest.- Build the folder roster: use
.context.md § Owners summarywhen it enumerates folders; otherwise groupFilenodes by top-level folder prefix (packages/<x>/src,src/<module>, etc.). - For each folder (top 15 by file count): resolve top owner and share from
{{ prefetch_path }} § ownerswhen present, else callmcp__codehub__owners({path: <folder>}). Capture top owner, share %, total contributors. - Rank folders by top-owner share, descending. Draft the ranking table with columns
Folder | Top owner | Share | Total contributors. Every Folder cell is a backtick path. - Identify Single Points of Failure: folders or files where the top owner's share is > 70%. For each SPOF: draft a bullet under the
## Single points of failureH2 stating the path, the owner's share percentage, and a one-sentence mitigation (pair reviewer, knowledge-transfer session, cross-training target, etc.). - Draft the intro (1-2 paragraphs): what "share" means (commit share, not line share), the window, and what a > 70% share signals for bus factor.
Write {{ docs_root }}/analysis/ownership.mdwith H1 ={{ repo }} · Ownership.
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 · 102 lines · 0 tokens per session scan A b0b6141769b5
doc-analysis-ownership 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,446 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.