Borrowing it
Nothing to install: this file belongs to darwin/supex. 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/darwin/supex/main/.claude/skills/commit-vendor/SKILL.mdgit clone --depth 1 https://github.com/darwin/supexWrote 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/skills/darwin/supex/commit-vendor)<a href="https://agentmods.dev/skills/darwin/supex/commit-vendor"><img src="https://agentmods.dev/badge/skills/darwin/supex/commit-vendor/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/skills/darwin/supex/commit-vendor"><img src="https://agentmods.dev/badge/skills/darwin/supex/commit-vendor.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.00011 | $0.00756 |
| Opus 5 | $0.00005 | $0.00378 |
| Sonnet 5 | $0.00002 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
commit-vendor 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit updated vendored submodule pointers in the supex repo. This command handles ONLY the commit step — fetching, reviewing, and testing are done by review-vendor.
All paths below are relative to the supex repo root.
Submodules
All vendored submodules (vcad/vendor/tang, vcad/vendor/loon, vcad/vendor/vcad) track upstream origin/main directly — no fork, no local patches. A pointer is always an upstream commit, so nothing has to be pushed before committing.
Step 1: Detect changed pointers
Check which submodules have changed pointers relative to the last supex commit:
git diff --submodule=short -- vcad/vendor/
git diff --cached --submodule=short -- vcad/vendor/
If no submodule pointers changed, report "nothing to commit" and stop.
Step 2: Compute upstream ranges
For each submodule with a changed pointer:
# SHA stored in supex repo (last commit)
old_upstream=$(git rev-parse HEAD:vcad/vendor/<name>)
# SHA currently in worktree
new_upstream=$(git -C vcad/vendor/<name> rev-parse HEAD)
Validate reachability
The new pointer MUST be reachable from the upstream remote, otherwise git clone --recurse-submodules breaks:
git -C vcad/vendor/<name> branch -r --contains $new_upstream | grep -q origin/ || echo "NOT ON UPSTREAM"
If a pointer is not on upstream (e.g. a local experiment), STOP and report — do not commit it.
Step 3: Show summary
Before committing, display a summary to the user:
For each changed submodule:
- Repo name
- Old upstream → new upstream (short SHAs)
- GitHub compare link:
https://github.com/ecto/<name>/compare/<old_upstream>...<new_upstream> - Number of new upstream commits:
git -C vcad/vendor/<name> rev-list --count $old_upstream..$new_upstream(a rollback shows 0 — say so)
Ask the user to confirm before proceeding.
Step 4: Commit
Create a single atomic commit with all changed submodule pointers and any modified build artifacts.
Stage all changes
# Stage all changed submodule pointers
git add vcad/vendor/tang vcad/vendor/loon vcad/vendor/vcad # only those that changed
# Stage Cargo.lock if modified by the rebuild
git diff --quiet -- vcad/sidecar/Cargo.lock || git add vcad/sidecar/Cargo.lock
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 · 90 lines · 11 tokens per session scan A 8a02fc59e6db
commit-vendor is a skill published in the GitHub repository darwin/supex (45 stars, last pushed 2d ago), licensed MIT. It adds 11 tokens to every session and 756 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-09-07.
Other skills, from other repositories
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
block-no-verify-hook
Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.