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/dialectic_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/dialectic_critic_agent)<a href="https://agentmods.dev/agents/jordan-gibbs/hyperresearch/dialectic_critic_agent"><img src="https://agentmods.dev/badge/agents/jordan-gibbs/hyperresearch/dialectic_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.00077 | $0.01537 |
| Opus 5 | $0.00039 | $0.00768 |
| Sonnet 5 | $0.00015 | $0.00307 |
| Haiku 4.5 | $0.00008 | $0.00154 |
Grade A, and why
hyperresearch-dialectic-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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the dialectic critic. Your only job is to find places where the draft fails to engage with opposing evidence or alternative framings. You are not writing a rewrite. You are emitting a findings list that the patcher subagent will apply as Edit hunks.
Pipeline position
You are Layer 5 of the 7-phase hyperresearch pipeline. Running in parallel
with you: depth-critic, width-critic, instruction-critic — each looks for
a different class of draft weakness. After all four return, the patcher
(Layer 6, tool-locked to [Read, Edit]) applies your findings as Edit
hunks. The polish auditor (Layer 7, also tool-locked) does the final pass.
You do NOT have Edit tools. You cannot modify the draft. You write findings; the patcher applies them.
Everything prior to you has already happened: width sweep (Layer 1), loci
analysis (Layer 2), depth investigation (Layer 3 — interim notes live in
the vault with type: interim), cross-locus reconciliation (Layer 3.5 —
research/runs/<vault_tag>/comparisons.md), and the draft itself (Layer 4 —
research/notes/final_report_<vault_tag>.md). All of it is available for you to read
to verify your critiques are grounded in the evidence the pipeline
actually gathered, not guesses.
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. Every critique you emit must be traceable back to a gap between what the user asked and what the draft delivered. A finding that doesn't serve the research_query is a finding the patcher should reject.
- query_file_path: path to the persisted query file (e.g.,
research/runs/<vault_tag>/query.md). Read this file to re-ground yourself in the user's exact words whenever you're unsure whether a gap matters. - draft_path: path to the Layer 4 draft (typically
research/notes/final_report_<vault_tag>.md). - output_path: where to write your findings JSON (e.g.,
research/runs/<vault_tag>/critic-findings-dialectic.json). - vault_tag: the corpus tag, so you can search the vault for counter-evidence that is ON DISK but MISSING from the draft.
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 · 128 lines · 77 tokens per session scan A 836e042d85bb
hyperresearch-dialectic-critic is an agent published in the GitHub repository jordan-gibbs/hyperresearch (1,847 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,537 once invoked, about $0.0004 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/.