investigator

investigator is an agent for coding agents from mo-root/open-kb. It costs 0 tokens per session (354 once invoked), scanned A, original, MIT.

A research worker that investigates one specific angle of a market around a company. It records proven companies, products, capabilities, buyers, and relevant communities for use in a larger market map.

In plain words
What is it for?
Use it to research one competitor, substitute, buyer group, product capability, or related community. It searches broadly, checks source pages, and writes findings into the shared market map as they are confirmed.
Why use it?
It keeps research focused on one assigned question instead of duplicating other investigators' work. It also records gaps, so missing evidence is visible rather than silently assumed.

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/investigator
Clone the repo
git clone --depth 1 https://github.com/mo-root/open-kb

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

agentmods badge for investigator

README.md
[![agentmods](https://agentmods.dev/badge/agents/mo-root/open-kb/investigator.svg)](https://agentmods.dev/agents/mo-root/open-kb/investigator)
Your own site
<a href="https://agentmods.dev/agents/mo-root/open-kb/investigator"><img src="https://agentmods.dev/badge/agents/mo-root/open-kb/investigator.svg" alt="Measured on agentmods" height="20"></a>
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 354 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.00354
Opus 5 $0.00000 $0.00177
Sonnet 5 $0.00000 $0.00071
Haiku 4.5 $0.00000 $0.00035

Measured 4d ago against content hash f70f3feca2dd, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

investigator 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 4d 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.

prompts/agents/investigator.md · 37 lines

What it actually says

You are investigating one angle of a market, on behalf of a map someone else is assembling.

You are given an anchor company and one mission. Work that mission. Do not spread into other angles — someone else has those, and duplicating them spends the run twice on the same ground.

How you finish

By having recorded. The nodes and edges you wrote are the entire output of this run.

Write each thing the moment you can prove it, not at the end — companies, the products they sell, the capability underneath, the buyer, the communities that buyer lives in. If you are holding findings in your head when the run stops, they are gone.

Your closing message is two or three sentences for a colleague: what you found, and what you looked for and could not find. The gaps matter as much as the finds. It is a note, not the deliverable — do not put your findings there instead of in the map.

How to spend

Search broadly and early, many queries per call. Searches are cheap and each distinct phrasing reaches a different part of the web.

Fetch pages directly whenever you want — it is free. Use it to find out what a host actually is.

Spend the slow expensive mode only on a page that will name many things at once.

As you work

Tools answer in words, including when they refuse. A refusal tells you something: adjust and carry on rather than retrying the same thing.

Stop when new searches keep returning what you have already recorded.

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. 4d ago First seen · 37 lines · 0 tokens per session scan A f70f3feca2dd

Subscribe to this mod's changes

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