What is consolidate-run?

A cross-repository findings command for one roadmap. It gathers notes from orchestration runs, matches repeated findings by ID, and proposes items to carry into a later roadmap.

Use it to collect and compare findings across repositories without changing the stored run state.

It prevents the same issue found in several repositories from remaining as separate, unconnected notes.

How bredmond1019/claude-sdk-rs configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bredmond1019/claude-sdk-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bredmond1019/claude-sdk-rs/main/.claude/commands/consolidate-run.md

Clone the repo

git clone --depth 1 https://github.com/bredmond1019/claude-sdk-rs

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/consolidate-run/github.svg)](https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/consolidate-run)

Your own site

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/consolidate-run"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/consolidate-run/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/bredmond1019/claude-sdk-rs/consolidate-run"><img src="https://agentmods.dev/badge/commands/bredmond1019/claude-sdk-rs/consolidate-run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,853 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00061	$0.02853
Opus 5.5	$0.00024	$0.01141
Sonnet 5.5	$0.00012	$0.00571
Haiku 4.5	$0.00006	$0.00285

Measured 11d ago against content hash 3f60b8debc83, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

consolidate-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 11d 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.

.claude/commands/consolidate-run.md · 185 lines

How it starts

The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Consolidate Run — gather findings across the fleet for one roadmap

Lane runs leave findings in their own repos (planning/orchestration-run/<roadmap-slug>/notes.md and review.md, per D57) and nothing gathers them. A defect observed once in four separate repos is four notes nobody correlates. This command implements D57 section 5 — it gathers, correlates by finding_id, and proposes; it does not decide, and it does not write state.

Related: the record contract itself (layout, frontmatter, origin_roadmap, lifecycle) is BT.ticket.orchestration-run-record-contract — this command depends on it and does not restate it. /generate-roadmap --from <consolidated> is the disposal path for what this command proposes.

Variables

$ARGUMENTS — a roadmap slug, plus optional flags.

Usage: /consolidate-run <roadmap-slug> [--repo <slug>]

Flag	Required	Default	What it does
`<roadmap-slug>`	yes	—	The roadmap whose records to consolidate. Matches the `roadmap:` frontmatter field on run records and resolves to `<roadmap-dir>` under `planning/roadmaps/` (or legacy `planning/`) per Step 1's resolution rule.
`--repo <slug>`	no	none (fleet-wide)	Scope discovery to one repo instead of the whole fleet.

Both scopes required by D57 section 5:

Run at the brain root with no --repo — consolidates the whole roadmap across every repo in the fleet. This is the normal case: the point of consolidation is cross-repo correlation.
Run inside one repo (or at the brain root with --repo <slug>) — consolidates that repo's records for the roadmap alone. Useful when a single lane needs its own findings reviewed before the fleet-wide run, or when only one repo's records exist yet.

Empty $ARGUMENTS → print usage and stop.

Step 1 — Resolve scope

Walk up from cwd for brain.toml to find BRAIN_ROOT. Resolve <roadmap-slug> to roadmap_dir via /begin-orchestration's Step 1C rule (planning/roadmaps/<roadmap-slug>/ first, then legacy planning/<roadmap-slug>/; both existing is an error) — cited here, not restated. If neither location exists, stop — there is nothing to consolidate into.

Read the full file on GitHub · 185 lines

Changes

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.

11d ago First seen · 185 lines · 61 tokens per session scan A 3f60b8debc83

Subscribe to this mod's changes

consolidate-run is a command published in the GitHub repository bredmond1019/claude-sdk-rs (23 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 61 tokens to every session and 2,853 once invoked, about $0.0002 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-10-26.

Planning Productivity

consolidate-run next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
consolidate-runbredmond1019/claude-sdk-rs	Command	23	1mo ago	Apache-2.0	A	61	Claude Code
wsdanielmiessler/LifeOS	Command	20k	yesterday	MIT	A	0	Claude Code
cancel-ralphanthropics/claude-plugins-official	Command	46k	yesterday	Apache-2.0	A	4	Claude Code
engage.actionshypnguyen1209/offensive-claude	Command	412	15d ago	MIT	A	11	Claude Code
focusData-Wise/claude-plugins	Command	7	yesterday	MIT	A	0	Claude Code
stuckData-Wise/claude-plugins	Command	7	yesterday	MIT	A	0	Claude Code
quickstartorq-ai/assistant-plugins	Command	6	2d ago	MIT	A	23	Claude Code

claude-sdk-rs: Command for Claude Code