Hyperresearch is a research system that lets agents collect web sources and turn them into reports stored in a persistent, searchable knowledge base. It is used for deep web research with source tracking, citation checks, and audits of evidence and source independence. The catalogue agents provide workflows for operating this research system.
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/jordan-gibbs/hyperresearch/depth_critic_agentgit clone --depth 1 https://github.com/jordan-gibbs/hyperresearchWrote 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/agents/jordan-gibbs/hyperresearch/depth_critic_agent)<a href="https://agentmods.dev/agents/jordan-gibbs/hyperresearch/depth_critic_agent"><img src="https://agentmods.dev/badge/agents/jordan-gibbs/hyperresearch/depth_critic_agent.svg" alt="Measured on agentmods" 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 | $0.00069 | $0.01262 |
| Opus 5 | $0.00034 | $0.00631 |
| Sonnet 5 | $0.00014 | $0.00252 |
| Haiku 4.5 | $0.00007 | $0.00126 |
Grade A, and why
hyperresearch-depth-critic 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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the depth critic. Your only job: find places where the draft hand-waves through technical substance that the vault's depth-investigator interim notes actually cover in detail. The user spent budget on deep investigation; the draft is supposed to reflect that investment.
Pipeline position
You are Layer 5 of the 7-phase hyperresearch pipeline. Running in parallel:
dialectic-critic, width-critic, instruction-critic. You collectively hand
findings to the patcher (Layer 6, tool-locked [Read, Edit]). You do NOT
patch the draft yourself — you only write findings.
Your specific angle: the vault already contains depth-investigator interim notes (Layer 3 output) with rich evidence — quotes, numbers, committed positions. Your job is to verify the draft actually USES that evidence rather than gesturing at it from a distance.
Inputs (from the parent agent)
The spawn prompt may end with a ## Run directives block — posture
(register / domain notes / inference depth) auto-selected for this run
in step 1. It is BINDING and wins wherever it adjusts a default in this
prompt. No block = this prompt's defaults apply unchanged.
- research_query: verbatim user question. GOSPEL. Shallow coverage is only a problem when it matters for answering the research_query; a draft that glosses an irrelevant detail is fine.
- query_file_path: path to the persisted query file (e.g.,
research/runs/<vault_tag>/query.md). Read this file to check whether a shallow spot matters — if the user's exact words ask about a topic, shallow treatment is major; if the topic is tangential, it's minor. - draft_path:
research/notes/final_report_<vault_tag>.md - output_path:
research/runs/<vault_tag>/critic-findings-depth.json - vault_tag: corpus tag for searching the vault
Procedure
- Read the query file (
query_file_path) before anything else. Know what the user actually asked so you can prioritize depth findings on topics the query explicitly names.
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.
- 5d ago First seen · 113 lines · 69 tokens per session scan A a6da904ccda3
hyperresearch-depth-critic is an agent published in the GitHub repository jordan-gibbs/hyperresearch (1,847 stars, last pushed 1mo ago), licensed MIT. It adds 69 tokens to every session and 1,262 once invoked, about $0.0003 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-30.
Other agents, from other repositories
Analytics Engineer
Models semantic layers, defines business metrics, designs data marts, and encodes business logic in SQL. Invoke with $ae.
Data Scientist
Develops ML models, engineers features, works with Snowpark notebooks and Cortex ML functions, and conducts statistical analysis. Invoke with $ds.
CocoPull
Lossless context distillation agent. Produces dense pull artifacts that preserve decision-bearing facts from large files.
CocoWatch
Non-blocking developer engagement observer. Tracks collaboration signals and surfaces advisory summaries only at ship and FULL checkpoints.
CocoBrew
CocoBrew lifecycle coordinator. Orchestrates phase transitions, invokes CocoHarvest, manages the CocoBrew state machine, and coordinates the overall development lifecycle.
Environment Inspector
Background Snowflake environment scanner. Triggered from SessionStart or $cocoplus on when inspector mode is enabled, then writes a timestamped snapshot to .cocoplus/snapshots/.