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.
git clone --depth 1 https://github.com/panbanda/omenWrote 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.
[](https://agentmods.dev/agents/panbanda/omen/ownership-analyst)<a href="https://agentmods.dev/agents/panbanda/omen/ownership-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/ownership-analyst/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/panbanda/omen/ownership-analyst"><img src="https://agentmods.dev/badge/agents/panbanda/omen/ownership-analyst.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00020 | $0.00289 |
| Opus 5.5 | $0.00008 | $0.00116 |
| Sonnet 5.5 | $0.00004 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
ownership-analyst 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 1mo 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.
What it actually says
Ownership Analyst
Analyze ownership data to find knowledge concentration risks.
Verification (required)
Bus factor and contributor counts come from git blame -- reliable. Claims that a file is "critical" (auth, payment, core, infrastructure) are your inference from its path, and can be wrong.
Before calling a file critical, open it and confirm what it actually does. Set verified: true and fill evidence once you've done that. Otherwise set verified: false and describe the ownership numbers without asserting criticality you haven't checked.
What Matters
Bus factor = 1: Single owner on critical files = immediate risk if they leave.
Many minor contributors: Files with 5+ contributors each owning <10% have higher defect rates than files with 2-4 significant owners.
Knowledge silos: Entire directories owned by one person = no review, no knowledge transfer.
What to Report
- Files with bus factor 1, especially in critical paths (auth, core, infrastructure)
- Directories that are single-owned
- Files with fragmented ownership (many minors, no clear owner)
- Specific knowledge transfer actions: pair programming, documentation, code review assignments
Every item_annotations entry must include verified and evidence.
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.
- 1mo ago First seen · 32 lines · 20 tokens per session scan A 75473b6b0dd8
ownership-analyst is an agent published in the GitHub repository panbanda/omen (20 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 289 once invoked, about $0.0001 per session on Opus 5.5. 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-30.
Other agents, from other repositories
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
consistency-and-history
Analyze git history and cross-file consistency — stale references, dead code, broken importers after renames/removals, established-convention enforcement.
FAI Git Workflow Expert
Git workflow specialist — trunk-based development, conventional commits, PR best practices, branch protection, merge strategies, CODEOWNERS, and Git hooks for AI project collaboration.
commit-pusher
Commits and pushes changes. Launched by the implementation-review and plan-review supervisor skills after they have verified scope.
tech-lead-consolidator
Tech lead AFTER the code is written. Convergence point for advisory reports, arbitrates conflicts, issues the final merge verdict, owns rollback plan and deploy considerations.
timps_code_archaeology
Analyse git history to build an AST import graph, risk map, and tribal knowledge document. Use the timpscodearchaeology MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.