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/mo-root/open-kb/triagegit clone --depth 1 https://github.com/mo-root/open-kbWhat 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.00000 | $0.00495 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
triage 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 2d 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
Sixty hosts came back from searches about one market. Before this run spends a fetch and a judgement on each, say which are worth it — from the search metadata alone.
The market: the anchor: {{anchor}} — {{sells}} its buyer: {{buyer}}
For each host below you have what the search engine itself said: how many distinct queries returned it, a page title, and a description. That is thin evidence, and the bar is set accordingly: you are not judging what a host IS — the judge does that later, from the host's own page. You are answering one cheaper question: could this host plausibly belong on a map of this market?
keep: true— anything that could be a vendor, a substitute, a tool, a directory, a publication, a community, a buyer, or infrastructure of this market. A map is the ecosystem, not a shortlist: a subreddit arguing about the anchor's category belongs, a review site ranking its vendors belongs, an open-source project doing the job belongs.keep: false— only when the metadata makes it plain the host has nothing to do with this market: a recipe blog surfaced by an unlucky word, a parked domain, a celebrity news page, a store selling physical goods into an unrelated trade. Write thewhyas the one line that makes it plain — it is recorded against the host as the reason it was never judged.
Skip is the destructive verdict: a skipped host is never fetched, never judged, and leaves the map carrying only your sentence. When the metadata leaves any room for doubt, keep. A kept irrelevance costs one cheap judgement that will settle it properly; a skipped vendor is a hole in the map nothing downstream can repair. If you find yourself reasoning about what a host sells or how good it is, you have left your question — that is the judge's work, keep it and move on.
Answer with verdicts: one row per host, every host answered, host copied exactly as given,
keep, and a short why for the skips ("kept" is enough for a keep).
The hosts, one per line — host, how many queries returned it, a title, a description:
{{hosts}}
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.
- 2d ago First seen · 38 lines · 0 tokens per session scan A 3d2d0fc72ff1
triage is an agent published in the GitHub repository mo-root/open-kb (11 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 495 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.
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.
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…
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…
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…
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…
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…