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.
git clone --depth 1 https://github.com/AgriciDaniel/ace-claude-codeWrote 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/commands/agricidaniel/ace-claude-code/discuss-phase)<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/discuss-phase"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/discuss-phase/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/agricidaniel/ace-claude-code/discuss-phase"><img src="https://agentmods.dev/badge/commands/agricidaniel/ace-claude-code/discuss-phase.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.00845 |
| Opus 5.5 | $0.00006 | $0.00338 |
| Sonnet 5.5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
ace:discuss-phase 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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use when you need to:
- Understand requirements better
- Explore technical options
- Get user preferences before planning
- Align on approach before execution
Required: @.ace/planning/STATE.md @.ace/planning/PROJECT.md @.ace/planning/ROADMAP.md
Optional: @.ace/planning/codebase/ (if brownfield) @.ace/planning/ISSUES.md (for context)
1. Load Phase Context
Read ROADMAP.md for:
- Phase goal
- Dependencies (what must be done first)
- Estimated scope
Read PROJECT.md for:
- Related requirements
- Technical constraints
- Previous decisions
2. Display Phase Overview
+==============================================================+
| DISCUSS PHASE [N] |
+==============================================================+
Phase: [N] - [Phase Name]
Goal: [Phase goal from ROADMAP.md]
Dependencies:
- Phase [X] (status: [Complete/In Progress])
- Phase [Y] (status: [Complete/In Progress])
Related Requirements:
- [Requirement 1 from PROJECT.md]
- [Requirement 2 from PROJECT.md]
+==============================================================+
3. Technical Context
If codebase/ exists, summarize:
Existing Code Context:
- Stack: [From STACK.md]
- Architecture: [From ARCHITECTURE.md]
- Relevant concerns: [From CONCERNS.md]
4. Discussion Prompts
Use AskUserQuestion to explore:
Question 1: Scope Clarification
"Looking at Phase [N], here's what I understand the goal to be: [Phase goal]
Is this accurate, or should we adjust the scope?"
- Options: "Accurate" / "Needs adjustment"
Question 2: Technical Approach
"For implementing [goal], I see a few approaches:
- [Approach A] - [brief description]
- [Approach B] - [brief description]
Which direction do you prefer?"
- Options: Based on approaches identified
Question 3: Priorities
"What's most important for this phase?"
- Options: "Speed" / "Quality" / "Simplicity" / "Flexibility"
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.
- 1mo ago First seen · 167 lines · 14 tokens per session scan A c031c66d4466
ace:discuss-phase is a command published in the GitHub repository AgriciDaniel/ace-claude-code (27 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 845 once invoked, about $0.0001 per session on Opus 5.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.