agentmods.dev

uv-sbom: Skill for Claude Code

.claude/skills/commit/SKILL.md

commit is a skill for Claude Code from Taketo-Yoda/uv-sbom. It costs 12 tokens per session (1,589 once invoked), scanned A, original, MIT.

A guided Git commit workflow that checks the current branch, runs code-quality checks, and creates commits using conventional commit messages. It refuses direct commits to protected branches such as main and develop.

In plain words
What is it for?
Use it to validate the branch, create or select an allowed working branch, run checks, and prepare an English commit with the required format.
Why use it?
It prevents accidental changes to protected branches and makes commit history more consistent and readable. It also gives the work a suitable feature, bugfix, hotfix, documentation, or refactoring branch when needed.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Taketo-Yoda/uv-sbom's own configuration. It tells Claude Code how to work on uv-sbom itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything uv-sbom configures →

not rated 6repo changed 20d ago A scan 12 tokens original MIT
View source ↗ Taketo-Yoda/uv-sbom
Reuse

Borrowing it

Nothing to install: this file belongs to Taketo-Yoda/uv-sbom. 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/Taketo-Yoda/uv-sbom/develop/.claude/skills/commit/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Taketo-Yoda/uv-sbom

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.

agentmods badge for commit

README.md
[![agentmods](https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/commit/github.svg)](https://agentmods.dev/skills/taketo-yoda/uv-sbom/commit)
Your own site
<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/commit"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/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.

agentmods 80×15 button for commit

Your own site · 80×15
<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/commit"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,589 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01589
Opus 5.5 $0.00005 $0.00636
Sonnet 5.5 $0.00002 $0.00318
Haiku 4.5 $0.00001 $0.00159

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

Security

Grade A, and why

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 20d 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/skills/commit/SKILL.md · 256 lines

How it starts

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

/commit - Commit Creation Skill

Create commits with proper code quality checks and conventional commit messages.

Language Requirement

IMPORTANT: All commit messages MUST be written in English.

Step 0: Verify Branch (MANDATORY)

CRITICAL: This step MUST be performed before any other step.

Check Current Branch

git branch --show-current

Branch Validation Rules

Current Branch Action
main ❌ STOP - Never commit directly to main
develop ❌ STOP - Never commit directly to develop
feature/* ✅ Proceed with commit
bugfix/* ✅ Proceed with commit
hotfix/* ✅ Proceed with commit
docs/* ✅ Proceed with commit
refactor/* ✅ Proceed with commit

If on develop or main

  1. STOP immediately - Do not proceed with commit
  2. Inform the user about the branch policy violation
  3. Create a feature branch: 
    git fetch origin
git checkout -b feature/<issue-number>-<description> origin/develop
  4. After branch creation, proceed with the commit workflow

Stacked Mode: origin/develop is the correct base here even when Stacked Mode is active — this error-recovery path only triggers on develop/main (not on any stack layer), and /commit must never infer a stack base. If these changes belong on a stack layer, say so instead of guessing; the user re-bases the new branch per .claude/conventions/branching.md → "Branch Base" before the commit proceeds.

Error Message Template

If on protected branch, display:

⚠️ ERROR: Cannot commit directly to '{branch_name}' branch.

This project uses Git Flow. Please create a feature branch first:
  git checkout -b feature/<issue>-<description> origin/develop

See .claude/conventions/branching.md for branching guidelines
(including Stacked Mode).

Pre-flight Checks (MANDATORY)

Note: cargo fmt is handled automatically by the .githooks/pre-commit hook. cargo clippy and cargo test are handled by the .githooks/pre-push hook at push time (canonical commands: .claude/conventions/ci-checks.md). Run make setup once to activate these hooks if you haven't already.

Read the full file on GitHub · 256 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.

  1. 20d ago Changed · +6 lines 2003b81717c4
  2. 25d ago Changed · -2 lines ce5d8ea4d290
  3. 1mo ago Changed · +9 lines d54b508bb763
  4. 1mo ago First seen · 243 lines · 12 tokens per session scan A 27ec0afff4c2

Subscribe to this mod's changes

commit is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,589 once invoked, about $0.0000 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-04.

CommitsGit and workflowPythonsbomsbom-generatorsbom-tooluv
Related

Other skills, from other repositories

safety

Check secret handling, staged changes and push targets, destructive Git operations, Docker image hygiene, and new dependencies before consequential coding actions. Use for commits, pushes, container builds or publishes, dependency additions, and explicit safety reviews.

langchain-ai/deepagents · 48 tokens

polyphony

Multi-agent orchestration with container-isolated workspaces — each agent session runs in its own Docker container with independent git branches.

alinaqi/maggy · 27 tokens

cuga-contributor-workflows

Run CUGA contributor workflows: Conventional Commits, create pull requests against origin with gh and PR templates, ruff check/format via uv, and the required design-impact, area, and readability labels before every push and pull request. Use when the user says commit, create a commit, push, create PR, pull request…

cuga-project/cuga-agent · 92 tokens

stacking-prs

Create and manage GitHub native Stacked PRs in this repo with the gh stack CLI. Use when asked to stack PRs, split a large change into a stack, add a layer to a stack, restack or rebase a stack, adopt existing branches or PRs into a stack, check out someone else's stack, or land a stack. Covers creating and submitting…

PostHog/posthog · 136 tokens

git-workflow

Git operations: commits, branches, PRs, and conflict resolution.

vstorm-co/pydantic-deepagents · 17 tokens

recreating-fork-prs

Re-creates a reviewed pull request from a fork on a branch in PostHog/posthog, so it can get the required checks and merge, while the contributor stays the commit author and GitHub credits them on the squash commit. Use when a fork PR fails with "Depot CI does not run fork pull requests", when its Backend CI on Depot…

PostHog/posthog · 120 tokens