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.
curl -O https://raw.githubusercontent.com/Taketo-Yoda/uv-sbom/develop/.claude/skills/pre-push/SKILL.mdgit 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/pre-push)<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/pre-push"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/pre-push/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/taketo-yoda/uv-sbom/pre-push"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/pre-push.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.01068 |
| Opus 5 | $0.00005 | $0.00534 |
| Sonnet 5 | $0.00002 | $0.00214 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
pre-push 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 7d 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 — 162 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pre-push - Pre-push Validation Skill
Final validation before pushing commits to remote repository.
Purpose
Validate branch conventions and push commits to remote. Quality checks (fmt, clippy, tests)
are delegated to the .githooks/pre-push hook, which runs automatically when git push executes.
Hook delegation:
cargo fmt --all -- --check,cargo clippy --all-targets --all-features -- -D warnings, andcargo test --allare all run by.githooks/pre-pushon everygit push. Runmake setuponce to activate the hook if you haven't already.
Validation Checklist
All of the following MUST pass before pushing:
1. Branch Naming Convention
git branch --show-current
Verify branch name follows convention based on Issue labels (priority order):
| Priority | Issue Label | Branch Prefix | Example |
|---|---|---|---|
| 1 | enhancement |
feature/ |
feature/84-agent-skills |
| 2 | bug |
bugfix/ |
bugfix/42-fix-parsing |
| 3 | refactor |
refactor/ |
refactor/30-cleanup-code |
| 4 | documentation |
doc/ |
doc/50-update-readme |
| 5 | (no label) | feature/ |
feature/99-misc-task |
Additional: hotfix/<issue>-<desc> for critical production fixes
FORBIDDEN branches for direct push:
main- Use PR onlydevelop- Use PR only (if applicable)
2. Remote Branch Target
git remote -v
git branch -vv
Verify:
- Pushing to correct remote (typically
origin) - Not accidentally pushing to upstream/fork
Steps
Step 1: Check Branch Name
BRANCH=$(git branch --show-current)
echo "Current branch: $BRANCH"
Verify:
- Matches naming convention
- Not on
mainordevelop - Issue number in branch name (if applicable)
Step 2: Verify Unpushed Commits
git log origin/$(git branch --show-current)..HEAD --oneline 2>/dev/null || git log --oneline -5
Review what will be pushed.
Step 3: Final Confirmation
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.
- 7d ago First seen · 162 lines · 11 tokens per session scan A 13cf03e02714
pre-push is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 1,068 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
github-copilot-upgrader
Use this to update the Github Copilot CLI/SDK.
precommit
Pre-commit checks — lint:fix -> build -> test.
precommit-fast
Quick pre-commit checks — lint:fix -> test.
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
temporal-python-testing
Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…