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 skills add sorrek/mcp --skill ownership-enrichmentgit clone --depth 1 https://github.com/sorrek/mcpWrote 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/skills/sorrek/mcp/ownership-enrichment)<a href="https://agentmods.dev/skills/sorrek/mcp/ownership-enrichment"><img src="https://agentmods.dev/badge/skills/sorrek/mcp/ownership-enrichment/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/skills/sorrek/mcp/ownership-enrichment"><img src="https://agentmods.dev/badge/skills/sorrek/mcp/ownership-enrichment.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.00081 | $0.00710 |
| Opus 5 | $0.00041 | $0.00355 |
| Sonnet 5 | $0.00016 | $0.00142 |
| Haiku 4.5 | $0.00008 | $0.00071 |
Grade A, and why
ownership-enrichment 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ownership Enrichment
Take the user's account list, append ownership columns, hand back a file in the same shape they gave you.
Steps
-
Read the file and find the domain column. Look for
website,domain,url, orcompany_url. Report how many rows have a usable domain and how many don't — rows without one can't be enriched and shouldn't be silently dropped. -
Quote the cost ceiling up front.
parent_companiesandpe_ownershipare both 70 credits per URL where something is found — a URL with no parent / no PE owner is free. That means you can state an exact maximum before anything runs:200 valid domains × 70 credits × 2 output types = at most 28,000 credits — less if some companies have no parent or aren't PE-backed. The exact price is on each completed run before downloading.
Check the balance with
check_creditsand confirm the user wants to proceed. If they only need one of the two types, say so — it halves the ceiling. -
Run the pipeline.
submit_batch(domains)→process_batch(batch_id, types)→ pollget_run_statusevery 10–30 seconds untilcompleted. Large batches take minutes. Don't poll in a tight loop. -
Download and join. Fetch the CSV from the download link (no auth header needed) and join back to the original rows on
input_url. Preserve every original column and every original row, including the ones that couldn't be enriched — leave those cells blank rather than dropping the row. -
Write the output. Same format the user gave you. If they uploaded
.xlsx, give back.xlsx. Name it clearly, e.g.accounts_enriched.xlsx. -
Summarize. How many matched, how many are PE-backed, how many are subsidiaries, and anything that stands out — a cluster of accounts under one parent is worth flagging unprompted.
Suggested columns to append
| Column | Source |
|---|---|
parent_company |
parent_companies |
parent_company_url |
parent_companies |
is_pe_backed |
derived from pe_ownership |
pe_firm |
pe_ownership |
pe_firm_url |
pe_ownership |
deal_type |
pe_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.
- 8d ago Changed · +3 lines c9fa6d54fea4
- 12d ago First seen · 58 lines · 81 tokens per session scan A c5966d282717
ownership-enrichment is a skill published in the GitHub repository sorrek/mcp (1 stars, last pushed 12d ago), licensed MIT. It adds 81 tokens to every session and 710 once invoked, about $0.0004 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-31.
Other skills, from other repositories
Launch Risk Assessment
Identify, categorize, and prioritize product launch risks, producing a risk matrix (probability × impact) with mitigation strategies. Use for launch risk, risk register, and go-to-market risk review.
gingiris-go-global
🇺🇸 AI Product / SaaS Go-Global Complete SOP — From competitor research to launch to monetization. A full-cycle playbook covering Phase 0-5 (market validation, positioning, first 100 users, user interviews, beta-to-growth) plus open-source launch, Product Hunt, Reddit, SEO/GEO, conversion, and org principles.…
gr-competitor-research
Your competitor just launched. You have no idea how they grew so fast. Should you reverse-engineer their website? Track their social media? Map their growth flywheel? This gives you the complete SOP — from Wayback Machine snapshots to X/Twitter propagation analysis to growth flywheel scoring. Built from 150+ AI…
product-hunt-playbook
It's 11pm before your launch. Your PH page is ready but you have no idea what actually moves the ranking algorithm. Upvotes? Comments? Time-of-day? This is the hour-by-hour operations manual from someone who's coached 30+ #1 finishes. What's inside: • Ranking algorithm deep-dive (it's not just upvotes — weighted…
ai-launch-playbook
Launch your AI product to global attention — the playbook behind Manus, Devin, and AFFiNE's breakout launches. Covers AI-specific GTM strategy, hype cycle management, waitlist tactics, and multi-market rollout for maximum day-one impact.
ai-product-launch
First AI Product Launch — Zero to Live in 30 Days. Step-by-step guide for shipping your first AI product from idea validation to paying customers. Includes day-by-day timeline and real examples. By @WeiYipei.