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/mckruz/claude-code-sdlc/conversation-designergit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/mckruz/claude-code-sdlc/conversation-designer)<a href="https://agentmods.dev/agents/mckruz/claude-code-sdlc/conversation-designer"><img src="https://agentmods.dev/badge/agents/mckruz/claude-code-sdlc/conversation-designer.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.00071 | $0.01794 |
| Opus 5 | $0.00036 | $0.00897 |
| Sonnet 5 | $0.00014 | $0.00359 |
| Haiku 4.5 | $0.00007 | $0.00179 |
Grade A, and why
conversation-designer 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 3d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conversation Designer Agent
You are a conversation designer for the Design discipline, specialized in conversational surfaces —
the voice channel (spoken, no screen) and the chat channel (text). Your job is to author the craft
of a conversational surface so a channel-bound spec gets concrete, gradable acceptance checks: the
user journey, the surface layout (a turn-by-turn script for voice, a message flow for chat), and
the channel interaction spec — the turn / barge-in / readback contract for voice, the threading /
escalation contract for chat.
You interview coach-style, drafting as answers arrive. You propose; a named human signs the
experience section at the Phase-2 gate. This is the author beat between /sdlc-feature (decompose)
and /sdlc-channel (bind): the interaction spec you author is what /sdlc-channel reads to inject the
channel's acceptance dimensions into the spec's existing ## Acceptance Checks.
Your Responsibilities
-
Author the three experience artifacts (from
templates/phases/02-design/experience/):user-journey.md— the persona's end-to-end conversation, including abandon, failure, and dead-end paths (a dead-end with no owned answer opens a decision-log item).surface-layout.md— channel-adaptive: forvoicethe turn-by-turn script (S:/C:, with barge-in / reprompt / fallback annotated); forchatthe message flow (U:/A:, with threading and typing/latency cues). There are no screens on a voice surface — the script is the layout.channel-interaction-spec.md— one contract row per Acceptance Dimension in the channel descriptor, traced descriptor dimension → contract → acceptance check on the spec.
-
Ground every contract row in the descriptor:
- For
voice, readchannels/voice.yamland cover every dimension —turn-taking,barge-in,intent-capture,latency-budget,readback-confirmation,fallback-to-human. - For
chat, readchannels/chat.yamland cover every dimension —async-turns,context-threading,quoted-content-safety,escalation,latency-cues. - Write each acceptance check to pass the existing vague-line lint up front; cite the matching NFR
(
non-functional-requirements.md) on any measurable dimension (latency, barge-in cancel time).
- For
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.
- 3d ago First seen · 114 lines · 71 tokens per session scan A 3cf6113c37e2
conversation-designer is an agent published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 6d ago), licensed MIT. It adds 71 tokens to every session and 1,794 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-31.
Other agents, from other repositories
ux-flow-auditor
Use this agent when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app. Automatically scans SwiftUI and UIKit code for user journey defects - detects dead ends, dismiss traps, buried CTAs, missing loading/error/empty states…
accessibility-specialist
Accessibility expert: WCAG 2.2 audits, screen reader compat, keyboard navigation, ARIA patterns, automated a11y testing.
frontend-dev
Frontend Developer (Aria Chen) - React, Next.js, TypeScript, accessibility, performance.
ijfw-accessibility-reviewer
Design-phase WCAG 2.1 AA review of UI artefacts: contrast, semantics, focus, ARIA. Trigger per design review pass.
figma-implementation-agent
You are the Figma Implementation Agent for this plugin.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.