orphan

A process for connecting isolated companies or other entities on a market map to the closest relevant participant, when the available descriptions support a relationship.

In plain words
What is it for?
Use it to identify competitors, substitutes, dependencies, integrations, publishers, directories, forums, or entities that genuinely have no supported connection.
Why use it?
It fills missing relationships without pretending that every entity must connect to another one.

Agent

Install

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.

agentmods
npx agentmods add agents/mo-root/open-kb/orphan
Clone the repo
git clone --depth 1 https://github.com/mo-root/open-kb
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 316 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00316
Opus 5 $0.00000 $0.00158
Sonnet 5 $0.00000 $0.00063
Haiku 4.5 $0.00000 $0.00032

Measured yesterday against content hash 87c0b8036480, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

orphan 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.

prompts/agents/orphan.md · 24 lines

What it actually says

These entities are on a market map of {{anchor}} — {{sells}} — and not one of them has an edge to any other player. Each was judged from its own page; what was never asked is where it STANDS.

For each numbered entity below: its own description, then the market's most prominent members as candidates. Say which single candidate it stands closest to, and how — or say it stands to nobody, which is a real answer and better than an invented edge.

  • to is one candidate's domain, exactly as written, or an empty string for nobody.
  • relation is how FROM stands to TO: competitor, substitute, dependency, integration, covers, lists, discusses — or unknown when an edge exists but none of these words fits.
  • The why is one line of HOW they relate, from the descriptions given. Never restate the label, and never invent a capability neither description claims: these edges ship marked as inferred, and an inferred edge earns its place by being arguable from what is on this page.

A publisher stands covers to a vendor it writes about; a directory lists what it indexes; a forum discusses the market's players; two vendors selling the same job to the same buyer are competitors; a tool the candidate plugs into is integration. One edge per entity, the strongest — the map needs each of these connected honestly once, not densely.

{{rows}}

Changes

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.

  1. yesterday First seen · 24 lines · 0 tokens per session scan A 87c0b8036480

Subscribe to this mod's changes

orphan is an agent published in the GitHub repository mo-root/open-kb (11 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 316 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-30.

Related

Other agents, from other repositories

research-orchestrator

Orchestrator agent for sigint research sessions. Owns all phase management: team lifecycle, dimension-analyst spawning, methodology verification, codex review gates, finding merge, progress tracking, delta detection, and cleanup. Spawned by start, update, and augment skills with mode-specific parameters.

zircote-plugins/sigint · 66 tokens

report-synthesizer

Use this agent when generating formal research reports from collected findings. This agent specializes in synthesizing data into executive-ready documents with visualizations. Examples: Context: Research is complete and user wants a report user: "Generate a report from my market research" assistant: "I'll use the…

zircote-plugins/sigint · 331 tokens

dimension-analyst

Use this agent for focused research on a single market dimension (competitive, sizing, trends, customer, tech, financial, regulatory). Parameterized by dimension — loads the relevant skill as methodology guide and writes findings to reports directory. Examples: Context: Orchestrator spawning parallel analysts user…

zircote-plugins/sigint · 187 tokens

issue-architect

Use this agent when converting research findings, recommendations, or analysis into actionable GitHub issues. This agent specializes in atomizing large initiatives into sprint-sized, well-structured issues. Examples: Context: Research has been completed and user wants action items user: "Convert these market research…

zircote-plugins/sigint · 350 tokens

falsification-analyst

Use this agent to perform adversarial falsification of sigint research findings. The agent treats each finding as a hypothesis under test, generates targeted disconfirming queries, executes web-only adversarial search, assigns a verdict (falsified | weakened | survived | inconclusive), and writes per-claim…

zircote-plugins/sigint · 263 tokens

source-chunker

Use this agent to process large documents that exceed context limits. Accepts a URL or file path, detects content type, partitions into chunks, spawns chunk analysts, and synthesizes findings. Examples: Context: Dimension analyst encounters a large report user: "Process this 50-page analyst report for competitive…

zircote-plugins/sigint · 187 tokens