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/consiliency/code-index-mcp/execute-lanegit clone --depth 1 https://github.com/Consiliency/Code-Index-MCPWhat 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.00020 | $0.01308 |
| Opus 5 | $0.00010 | $0.00654 |
| Sonnet 5 | $0.00004 | $0.00262 |
| Haiku 4.5 | $0.00002 | $0.00131 |
Grade A, and why
execute-lane 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute Swim Lane with Parallel Sub-Agents
Inputs
$1= Phase document path (e.g.,plans/phase-2-ingestion.md)$2= Swim lane identifier (e.g.,SL-1,lane-api-routes, etc.)
Execution Strategy
1. Load Phase Plan & Extract Swim Lane
Read the phase implementation document:
@$1
Locate swim lane $2 within the document. Extract:
- Swim lane scope: Component boundaries, files, interfaces owned
- Task list: Individual work items with their dependencies
- Interface contracts: Frozen interfaces this lane depends on or provides
- Acceptance criteria: Definition of done for this lane
2. Verify Preconditions
Before spawning agents, check:
Interface Dependencies:
- All interfaces this lane consumes must be frozen (have
IF-*gate marked complete) - If any dependency is not ready, list them and STOP with message:
⚠️ Cannot proceed - waiting on interface freeze gates:
- IF-0-xyz: [description]
Recommend: Execute dependent lanes first or request interface definition
Git State:
- Current branch: !
git branch --show-current - Verify branch matches expected feature branch for this phase
- Check for uncommitted changes: !
git status --short - If dirty, warn but allow continuation (agents will commit their changes)
File Conflicts:
- Check if any files in this lane's scope are already modified in working tree
- List conflicts and ask user to confirm continuation
3. Task Dependency Analysis
From the task list for lane $2:
- Build dependency graph (which tasks can run in parallel vs sequential)
- Identify tasks with no dependencies ("ready" tasks)
- Group related tasks that should execute sequentially in one agent
Grouping heuristics:
- Tasks touching the same file → same agent (sequential)
- Tasks with direct data dependencies → same agent (sequential)
- Tasks on different files with no dependencies → parallel agents
- Avoid creating more than 5 parallel agents (diminishing returns)
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 · 187 lines · 0 tokens per session scan A 07480696a8c9
execute-lane is a command published in the GitHub repository Consiliency/Code-Index-MCP (57 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,308 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.