Borrowing it
Nothing to install: this file belongs to yugabyte/yugabyte-db. 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/yugabyte/yugabyte-db/master/.claude/commands/backport-commit.mdgit clone --depth 1 https://github.com/yugabyte/yugabyte-dbWrote 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/yugabyte/yugabyte-db/backport-commit)<a href="https://agentmods.dev/commands/yugabyte/yugabyte-db/backport-commit"><img src="https://agentmods.dev/badge/commands/yugabyte/yugabyte-db/backport-commit/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/yugabyte/yugabyte-db/backport-commit"><img src="https://agentmods.dev/badge/commands/yugabyte/yugabyte-db/backport-commit.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.00018 | $0.02389 |
| Opus 5.5 | $0.00007 | $0.00956 |
| Sonnet 5.5 | $0.00004 | $0.00478 |
| Haiku 4.5 | $0.00002 | $0.00239 |
Grade A, and why
backport-commit 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 9d 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.
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.
- 9d ago Changed · -10 lines 1069802530ae
- 11d ago Changed f183f5e1ecfd
- 19d ago Changed · +2 lines facff8a89f60
- 2mo ago First seen · 159 lines · 18 tokens per session scan A 73f3d9894a67
backport-commit is a command published in the GitHub repository yugabyte/yugabyte-db (10,636 stars, last pushed today), with no licence file. It adds 18 tokens to every session and 2,389 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.
Other commands, from other repositories
update
Refresh the committable tree-sitter symbol index (.vts-index) when it has gone STALE — one incremental re-index so the syntactic tier answers CURRENT code, not the state it was built at. Use when searchsymbol shows "SYNTACTIC · STALE", after a big branch switch / pull / large refactor, or when the file:line answers…
design.pre-hook
Runs before /design's phase 1 (Spec Author). Enforces the kit's invariant: every git branch gets a Lakebase branch, the SCM workflow state machine tracks that pairing, and lakebase-scm-claim-feature-branch is the only supported claim path.
release
Prepare a release using a strict verification-first workflow.
dbt-migration-batch-raise
Register-driven PR shipping pipeline: derive gate-passing candidates, smoke-build from the client branch, pre-raise comparison, drop-on-defect, raise with evidence-first body.
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.