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/ololand-ai/ololand-pluginsWrote 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/commands/ololand-ai/ololand-plugins/company-discovery)<a href="https://agentmods.dev/commands/ololand-ai/ololand-plugins/company-discovery"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/company-discovery/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/commands/ololand-ai/ololand-plugins/company-discovery"><img src="https://agentmods.dev/badge/commands/ololand-ai/ololand-plugins/company-discovery.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.00026 | $0.00395 |
| Opus 5 | $0.00013 | $0.00198 |
| Sonnet 5 | $0.00005 | $0.00079 |
| Haiku 4.5 | $0.00003 | $0.00040 |
Grade A, and why
company-discovery 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 9d 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
Company Discovery
Use this command when the user wants to discover companies, screen a market, search by natural-language criteria, or find sourcing candidates before creating a watchlist or deal.
Usage
/company-discovery "vertical SaaS payments companies with sponsor ownership" both
/company-discovery "industrial distributors in the Midwest with succession risk" private
Execution
- Prefer
mcp__ololand__natural_language_company_searchfor prose queries with multiple criteria. It decomposes intent and filters. - Use
mcp__ololand__search_company_discoverywhen the user supplies structured filters, mode, company scope, or wants lookup/discover/signals explicitly. - For each promising result, present the canonical name, domain/ticker when present, source summary, signal count, and why it matched.
- If the user wants ongoing monitoring, route to
/watchlistand callmcp__ololand__create_watchlistwith the same criteria. - If the user wants to diligence a result immediately, use
/new-dealormcp__ololand__create_dealwith the selected company.
Output
Render a concise table:
| Company | Type | Domain/Ticker | Match reason | Signals | Next action |
Then summarize:
- Query interpretation and filters applied.
- Degraded sources, if any.
- Recommended watchlist criteria if the user wants continuous monitoring.
Guardrails
- Do not create a deal automatically from a discovery result unless the user asks.
- Do not claim a result is proprietary if it came from public/signal sources.
- For investment recommendations, move from discovery into
/pre-screenor/dd-analyze.
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.
- 9d ago First seen · 43 lines · 26 tokens per session scan A 02589fc1721c
company-discovery is a command published in the GitHub repository ololand-ai/ololand-plugins (0 stars, last pushed 5d ago), licensed Apache-2.0. It adds 26 tokens to every session and 395 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-31.
Other commands, from other repositories
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…
audit
Scan for non-kernel money math. Rebuild critical flows as JournalEntrys. Replay and prove. Complements /ledger-verify.