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/databricks-solutions/consortWrote 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/databricks-solutions/consort/start)<a href="https://agentmods.dev/commands/databricks-solutions/consort/start"><img src="https://agentmods.dev/badge/commands/databricks-solutions/consort/start/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/databricks-solutions/consort/start"><img src="https://agentmods.dev/badge/commands/databricks-solutions/consort/start.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.00055 | $0.13308 |
| Opus 5.5 | $0.00022 | $0.05323 |
| Sonnet 5.5 | $0.00011 | $0.02662 |
| Haiku 4.5 | $0.00006 | $0.01331 |
Grade A, and why
start 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 today.
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- today Changed 3c63768308cb
- 2d ago Changed 3a578aa0b2fd
- 3d ago Changed af7487938a1c
- 5d ago Changed 9e77c601caca
- 6d ago Changed · -3 lines 27e83a4efdf3
- 8d ago Changed · +1 lines cc174342fada
- 20d ago Changed f40fce65743f
- 21d ago Changed 0c7f85ef8d6b
- 23d ago Changed 4fe33ed236ed
- 26d ago First seen · 320 lines · 55 tokens per session scan A 95f3a20cde32
start is a command published in the GitHub repository databricks-solutions/consort (33 stars, last pushed yesterday), with no licence file. It adds 55 tokens to every session and 13,308 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-09-21.
Other commands, from other repositories
spec-impl
Execute spec tasks using TDD methodology.
kiro-spec-impl
Command "kiro-spec-impl" from gotalab/cc-sdd, covering implementation task executor, core task, execution steps, step 1: load context and step 2: select tasks.
build
Plan-then-execute against SPEC.md. Native Claude Code loop, no sub-agents.
build
Run /build — see .claude/commands/build.md for the authoritative spec.
validate
Run /validate — see .claude/commands/validate.md for the authoritative spec.
test
Run /test — see .claude/commands/test.md for the authoritative spec.