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/linxule/interpretive-orchestration/dialogical-codergit clone --depth 1 https://github.com/linxule/interpretive-orchestrationWhat 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.00047 | $0.04331 |
| Opus 5 | $0.00023 | $0.02166 |
| Sonnet 5 | $0.00009 | $0.00866 |
| Haiku 4.5 | $0.00005 | $0.00433 |
Grade A, and why
dialogical-coder 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday First seen · 620 lines · 47 tokens per session scan A 56b9498e8e28
dialogical-coder is an agent published in the GitHub repository linxule/interpretive-orchestration (17 stars, last pushed 1mo ago), with no licence file. It adds 47 tokens to every session and 4,331 once invoked, about $0.0002 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
kaggle-miner
Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples.
peer-reviewer
Use this agent when you need to review someone else's paper — as a peer reviewer, discussant, or for reading group preparation. This agent reads the PDF carefully using split-pdf methodology, spawns parallel sub-agents for citation validation, novelty assessment, and methodology review, scans for hidden prompt…
code-review
Multi-persona orchestrator for adversarial review of R, Python, Julia, or Stata research scripts. Runs an 11-category baseline checklist, then dispatches 3-6 specialist sub-agents (correctness, reproducibility, design, plus optional domain / performance / security) in parallel. Deduplicates findings across reviewers…
fatal-error-check
Fast pre-review check for fatal errors in LaTeX papers. Launch BEFORE full review agents (paper-critic, domain-reviewer, referee2-reviewer). Binary PASS/FAIL verdict in 15-30 seconds. Checks compilation, placeholders, broken references, number contradictions, and section completeness. Examples: Example 1: user: "Quick…
literature-scout
经济金融学术文献侦察子智能体。负责系统性检索、筛选和分析学术文献，构建引文网络，识别研究缺口。与 generator-reviewer 分离原则：scout 只负责侦察，不参与评分和写作。.
orchestrator
Agent "orchestrator" from stephenlzc/AI-Powered-Literature-Review-Skills, covering orchestrator agent 模板, agent 信息, 核心原则, 系统架构 and 8阶段工作流.