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 commands/urav06/dialectic/debate-rungit clone --depth 1 https://github.com/urav06/dialecticWhat 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.00007 | $0.00290 |
| Opus 5 | $0.00003 | $0.00145 |
| Sonnet 5 | $0.00001 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
debate-run 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 2d 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
Run Debate
List available debates by checking for directories with debate.md files.
Arguments
$1: Debate slug (optional if only 1 debate exists)$2: Number of exchanges (optional, will ask if not provided)
Behavior
Determine Debate Slug
If $1 provided:
- Validate it exists
- Use it
If no $1:
- List debates from context above
- If 0: "No debates found. Create one with
/debate-new" - If 1: Auto-use that debate
- If 2+: "Which debate? {list}"
Determine Exchange Count
If $2 provided:
- Use it
If no $2:
- Ask: "How many exchanges?"
Execution
Once both parameters are validated:
Invoke the debate-orchestrator skill with:
- Debate slug: {slug}
- Number of exchanges: {N}
The skill manages:
- State machine progression (awaiting_arguments → awaiting_judgment cycles)
- Parallel debater coordination and judge evaluation
- Argument file creation and scoring
- State persistence across interruptions
Completion
The skill reports final scores when all exchanges complete.
Run /debate-report {slug} to generate comprehensive debate report and visualization.
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.
- 2d ago First seen · 56 lines · 0 tokens per session scan A ca1e48d55f0e
debate-run is a command published in the GitHub repository urav06/dialectic (6 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 290 once invoked, about $0.0000 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 commands, from other repositories
convert-to-todowrite-tasklist-prompt
Purpose: Transform verbose, context-heavy slash commands into efficient TodoWrite tasklist-based methods with parallel subagent execution for 60-70% speed improvements.
cleanup-context
You are a memory bank optimization specialist tasked with reducing token usage in the project's documentation system while maintaining all essential information and improving organization.
batch-operations-prompt
Optimize prompts for multiple file operations, parallel processing, and efficient bulk changes across a codebase. This helps Claude Code work more efficiently with TodoWrite patterns.
convert-to-test-driven-prompt
Transform user requests into Test-Driven Development (TDD) style prompts that explicitly define expected outcomes, test cases, and success criteria before implementation.
check-best-practices
Analyze code against language-specific best practices, coding standards, and community conventions to improve code quality and maintainability.
security-audit
Perform a comprehensive security audit of the codebase to identify potential vulnerabilities, insecure patterns, and security best practice violations.