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/pr/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/pr)<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/pr"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/pr/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/pr"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/pr.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.00012 | $0.02474 |
| Opus 5 | $0.00006 | $0.01237 |
| Sonnet 5 | $0.00002 | $0.00495 |
| Haiku 4.5 | $0.00001 | $0.00247 |
Grade A, and why
pr 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 5d 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 — 336 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/pr - Pull Request Creation Skill
Create Pull Requests that pass CI before creation and target the correct branch.
Language Requirement
IMPORTANT: All Pull Requests MUST be written in English.
- PR title: English
- PR body: English
- Commit messages: English
Pre-flight Checks (MANDATORY)
Before creating a PR, ALL of the following checks MUST pass:
1. Format Check
cargo fmt --all -- --check
If this fails, run cargo fmt --all to fix and commit the changes.
2. Clippy Check
cargo clippy --all-targets --all-features -- -D warnings
CRITICAL: Zero warnings required. Fix all issues before proceeding.
3. Test Suite
cargo test --all
All tests must pass.
Steps
Step 1: Run Pre-flight Checks
Execute all three checks above. If any fail:
- Fix the issues
- Commit the fixes using
/commitskill - Re-run the checks until all pass
WIRE Annotation Notice (informational — does not block)
git diff origin/develop...HEAD | grep -E '^\+.*WIRE\(#[0-9]+\)' | grep -v '^+++'
If the output is non-empty, print:
⚠️ This PR introduces WIRE(#N) annotation(s). Verify that Issue #N is open and will consume these items. The annotation will be auto-detected by /implement Step 4.0 when Issue #N is implemented.
This check is informational only and does not block PR creation.
Step 2: Verify Branch Status
# Check current branch
git branch --show-current
# Check if up to date with remote
git status
Verify:
- Not on
mainbranch (direct commits to main are forbidden) - Branch follows naming convention:
feature/<issue-number>-<description>for featuresbugfix/<issue-number>-<description>for bug fixeshotfix/<issue-number>-<description>for hotfixesdocs/<issue-number>-<description>for documentationrefactor/<issue-number>-<description>for refactoring
Step 3: Determine Base Branch
CRITICAL: This project uses develop as the integration branch.
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.
- 5d ago First seen · 336 lines · 12 tokens per session scan A a6a4fb4ddd8f
pr is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 2,474 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.
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…
mem0-integrate
Integrate Mem0 into an existing repository using a goal-driven, TDD pipeline. Detects the repo's language automatically and asks the user to pick between Mem0 Platform (managed) and Mem0 Open Source (self-hosted). Writes failing tests before any implementation. Produces a local feature branch plus .mem0-integration/…
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.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
nw-quality-framework
Quality gates - 11 commit readiness gates, build/test protocol, validation checkpoints, and quality metrics.