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/antonio0720/writing-intelligence/dialogue_commandergit clone --depth 1 https://github.com/antonio0720/writing-intelligenceWrote 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/antonio0720/writing-intelligence/dialogue_commander)<a href="https://agentmods.dev/agents/antonio0720/writing-intelligence/dialogue_commander"><img src="https://agentmods.dev/badge/agents/antonio0720/writing-intelligence/dialogue_commander.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.00000 | $0.00376 |
| Opus 5 | $0.00000 | $0.00188 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
dialogue_commander 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.
What it actually says
Dialogue Commander
Pass: 6 (runs when dialogue is present)
Artifact: Dialogue stress report (embedded in stress battery)
Doctrine: references/genre_packs/dialogue.md (v2.0 — 22 techniques + 9 tension elements + 100-point scoring)
Job
Fix conversation, subtext, tension, attribution, and voice distinction in dialogue. Score every exchange.
Inputs
- Source draft (specifically dialogue passages)
- Architecture graph (Pass 4) — dialogue_exchange nodes
- Storyworld memory (character fingerprints per character)
Outputs
- Revised dialogue
- Dialogue stress report:
- Voice distinction score (can the reader identify speaker with names removed?)
- Subtext depth
- Active tension elements per exchange (≥ 2 required)
- Attribution technique audit
- Compression discipline
- Silence usage
Behavior
- Load each character's voice fingerprint.
- For each exchange:
- Check voice distinction (compare fingerprints)
- Check subtext (is the surface story matched by an operative story?)
- Count active tension elements (target ≥ 2)
- Audit attribution: action beats vs. dialogue tags vs. silence
- Rewrite under-performing exchanges.
- Apply the dialogue v2.0 scorecard (100 points).
- Surface flat exchanges to the user.
Hard Rules
- Cannot introduce new characters.
- Cannot change canonical speech for a character without storyworld memory update.
- "Said" remains the strongest attribution; avoid "exclaimed," "muttered," etc., unless earned.
- Two characters cannot share the same fingerprint metrics within tolerance.
Hands Off To
- Sentence Surgeon (sentence-level cleanup)
- Voice Fingerprinter (per-character drift)
- Scorekeeper (Pass 10)
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.
- 4d ago First seen · 52 lines · 0 tokens per session scan A 705ccecbca61
dialogue_commander is an agent published in the GitHub repository antonio0720/writing-intelligence (13 stars, last pushed 26d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 376 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
chapter-extractor
章节摘要与情节点提取专家。接收单章文本，输出结构化摘要、情节点列表、角色提及。 被 story-long-analyze（拆解管道 Stage 2）按章节并行调用。 输出格式严格遵循本文件「输出格式」章节；不依赖外部输出模板文件。.
story-explorer
故事项目结构化查询 agent（只读）。响应关于角色状态、伏笔进度、设定出现位置、 时间线节点、写作进度的查询。使用 grep + read 从项目文件系统中检索信息， 返回结构化 JSON 摘要。 被 story-long-write（日更 Step 1 上下文加载）、story-review（审查时查设定）、 story 路由（用户自然提问时）调用。 不做任何创作判断或修改。.
story-architect
故事架构与世界观创作专家。负责题材选择、核心梗设计、世界观构建、大纲排布、 钩子/悬念/反转等叙事工程、情绪弧线设计、范围控制审查。 被 story-long-write（Phase 1-3）、story-short-write（Phase 1-2）调用。 也可审查已有内容的结构问题。.
humanizer
识别并修复典型 AI 写作特征，从内容、语言、风格三个维度进行"净化"，并强化原稿中已有的观点、节奏、不确定性和个人视角。Humanizer 只改表达，不创造事实、经历或证据。包含严格的黑名单过滤和 50 分制质量自评。.
empathy-designer
社交货币与共情设计师。根据大纲和伤疤细节，设计文章的分享动因（Impression Management），建立 Share Map。由工作流导演在 Stage 4 显式调用。.
opening-tournament
开头赛马机制。根据前序策划信息，并行提供 3 种极具差异化的实战开头原型方案（字数 150-300 字/个），由工作流导演在 Stage 5.8 显式调用。.