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/panbanda/omen/ownership-analystgit 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.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00289 |
| Opus 5 | $0.00010 | $0.00144 |
| Sonnet 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 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.
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.
- 5d ago First seen · 32 lines · 20 tokens per session scan A 75473b6b0dd8
ownership-analyst is an agent published in the GitHub repository panbanda/omen (19 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 289 once invoked, about $0.0001 per session on Opus 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
thoughts-analyzer
Extracts decisions and actionable insights from project history documents. Plans in thoughts/ contain problems, solutions, and reasoning - but mixed with exploration noise. Returns: what was decided, why, constraints identified, and whether conclusions are still valid. Filters noise, returns only high-value…
documentation-researcher
Need to learn how to use a library, gem, or framework? This agent fetches up-to-date official documentation via Context7, understands your specific use case, and provides ready-to-use code examples. Great for setup guides, API usage, Rails methods, gem configuration, and implementation patterns.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
review-tests-minitest
Minitest test quality and coverage reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-tests-minitest in repos that test with minitest. Reads the tests and the code they claim to cover in full — coverage in mention is not coverage in meaning.
review-docs
Documentation reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-docs with artifact paths. Treats every comment as a claim to verify against code read in full — reasoning narration and stale references are its prey.
review-performance
Performance reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-performance with artifact paths. Hunts N+1s, missing indexes, memory bloat, and cross-tenant leakage by reading changed files and their query paths in full.