Borrowing it
Nothing to install: this file belongs to Consiliency/Code-Index-MCP. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Consiliency/Code-Index-MCP/main/.claude/commands/do-next-steps.mdgit clone --depth 1 https://github.com/Consiliency/Code-Index-MCPWrote 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/consiliency/code-index-mcp/do-next-steps)<a href="https://agentmods.dev/commands/consiliency/code-index-mcp/do-next-steps"><img src="https://agentmods.dev/badge/commands/consiliency/code-index-mcp/do-next-steps/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/consiliency/code-index-mcp/do-next-steps"><img src="https://agentmods.dev/badge/commands/consiliency/code-index-mcp/do-next-steps.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.00000 | $0.01823 |
| Opus 5.5 | $0.00000 | $0.00729 |
| Sonnet 5.5 | $0.00000 | $0.00365 |
| Haiku 4.5 | $0.00000 | $0.00182 |
Grade A, and why
do-next-steps 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 2mo 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
do-next-steps
Execute the next implementation steps for any codebase using interface-driven parallel development to maximize agent productivity and ensure clean architecture.
METHODOLOGY: INTERFACE-DRIVEN PARALLEL DEVELOPMENT
This command analyzes any codebase's documentation structure (README.md, ROADMAP.md, architecture/ directory, AGENTS.md files) to create and execute a comprehensive implementation plan that maximizes parallelism through interface-based development.
DISCOVERY PHASE
1. Analyze Project Documentation
# Discover current project state dynamically
find . -name "README.md" -o -name "ROADMAP.md" -o -name "*.md" | head -20
find . -type d -name "architecture" -o -name "docs" -o -name "design"
find . -name "AGENTS.md" -o -name "CLAUDE.md" | sort
Extract Key Information:
- Project purpose and scope (from README.md)
- Implementation status and next steps (from ROADMAP.md)
- Architecture components and gaps (from architecture/ directory)
- Current implementation percentage (from status indicators)
- Critical path items (blocking other work)
- Parallel execution opportunities (independent components)
2. Identify System Architecture
# Discover architectural components
find . -name "*.puml" -o -name "*.dsl" -o -name "*architecture*"
ls -la */interfaces/ */contracts/ */api/ 2>/dev/null || echo "No existing interfaces"
find . -name "*interface*" -o -name "*contract*" -o -name "*protocol*"
Analyze Architecture Patterns:
- Layered architecture (API, Business, Data layers)
- Microservices (independent services)
- Plugin/Extension systems (dynamic loading)
- Event-driven (pub/sub patterns)
- Modular monolith (domain boundaries)
3. Assess Implementation Gaps
# Identify implementation vs design gaps
find . -name "*stub*" -o -name "*todo*" -o -name "*placeholder*"
grep -r "NotImplementedError\|TODO\|FIXME\|XXX" --include="*.py" --include="*.js" --include="*.ts"
find . -name "*test*" | wc -l # Test coverage indicator
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.
- 2mo ago First seen · 272 lines · 0 tokens per session scan A a1f51c0316a7
do-next-steps is a command published in the GitHub repository Consiliency/Code-Index-MCP (60 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,823 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.
do-next-steps compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| do-next-stepsConsiliency/Code-Index-MCP | Command | 60 | yesterday | MIT | A | 0 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |