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.
npx agentmods add skills/taketo-yoda/uv-sbom/commitnpx skills add Taketo-Yoda/uv-sbom --skill commitgit clone --depth 1 https://github.com/Taketo-Yoda/uv-sbomWrote 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/taketo-yoda/uv-sbom/commit)<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="Measured on agentmods" 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 | $0.00012 | $0.01355 |
| Opus 5 | $0.00006 | $0.00678 |
| Sonnet 5 | $0.00002 | $0.00271 |
| Haiku 4.5 | $0.00001 | $0.00136 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 243 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
- STOP immediately - Do not proceed with commit
- Inform the user about the branch policy violation
- Create a feature branch:
git fetch origin git checkout -b feature/<issue-number>-<description> origin/develop - After branch creation, proceed with the commit workflow
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/instructions.md for branching guidelines.
Pre-flight Checks (MANDATORY)
Note:
cargo fmtis handled automatically by the.githooks/pre-commithook.cargo clippyandcargo testare handled by the.githooks/pre-pushhook at push time. Runmake setuponce to activate these hooks if you haven't already.
1. Security Check
Verify no secrets in staged files:
- No API keys
- No passwords or credentials
- No tokens or secret strings
- No
.envfiles with real values - No
credentials.jsonor similar
Files to check: git diff --cached --name-only
If secrets are found:
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 First seen · 243 lines · 12 tokens per session scan A 27ec0afff4c2
commit is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (5 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 1,355 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-04.
Other skills, from other repositories
dependabot-pr-automation
Reviews open Dependabot pull requests, assesses their risk level based on version bump type and CI status, approves low-risk PRs, and merges them. Use when asked to process, review, merge, or triage Dependabot PRs.
commit
Safe commit with branch verification and build/test/lint checks.
review-diff
Pre-push diff review by the local GitHub Copilot CLI (gpt-5.6-sol, a separate-vendor LLM). Usage: /review-diff [BASEREF | --cached] (default base=origin/main).
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
commit-push-pr
Commit selected local changes, push the branch, and create or update a GitHub pull request with BitFun attribution. Use when the user asks to 提交 PR、提代码、commit and push、开 PR、create a pull request, or wants a Claude Code-like one-command PR publishing flow from BitFun.