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/implement/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/implement)<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/implement"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/implement/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/implement"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00013 | $0.03710 |
| Opus 5.5 | $0.00005 | $0.01484 |
| Sonnet 5.5 | $0.00003 | $0.00742 |
| Haiku 4.5 | $0.00001 | $0.00371 |
Grade A, and why
implement 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 18d 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/implement - Issue Implementation Skill
Orchestrates the complete workflow for implementing a GitHub issue, from branch creation to PR submission.
Language Requirement
IMPORTANT: All outputs (commits, PRs) MUST be written in English.
Workflow Overview
Issue Analysis → Branch Creation → [Planning] → Implementation → Commit → PR Creation
↑ Opus ↑ Sonnet
Stacked Mode (opt-in)
Stacked Mode (each PR based on the previous still-open PR's branch) is defined —
including its entry rule (explicit user request only; never inferred), why it is
opt-in, and its session-scoped, sticky scope — in
.claude/conventions/branching.md → "Stacked Mode (opt-in)". Read that section
before Step 3 whenever the user has mentioned stacking in this session. The safe
default is Normal Mode.
Steps
Step 1: Analyze Issue (MANDATORY)
gh issue view <issue-number>
Read the ENTIRE body, including the collapsed block. Issues follow the two-section
format in .claude/issue-guidelines.md: a visible human section and an AI section
collapsed under <details><summary>🤖 Implementation Spec (for AI agents)</summary>.
gh issue view returns the raw Markdown, so the collapsed content IS present in the
output — but it is easy to skim past. The implementation specification lives there.
Never plan from the human section alone.
Extract:
| From | Section | Use |
|---|---|---|
| Human | ## Summary / ## Why |
Issue intent; PR description |
| Human | ## Scope (In / Out) |
What must NOT be implemented |
| Human | ## Design Sketch |
Types to create/change (Mermaid, if present) |
| Human | ## Acceptance Criteria |
Behavior-level completion check |
| Labels | — | Branch prefix (Step 2) |
AI (<details>) |
## Context & Constraints |
Invariants, precedent Issues/PRs, files not to touch |
AI (<details>) |
## Design Decisions |
Approach already decided — do not re-litigate |
AI (<details>) |
## Files to Update/Create |
Files to read for Step 3.5 context |
AI (<details>) |
## Technical Acceptance Criteria |
Toolchain/docs gates before /commit |
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.
- 18d ago Changed · +8 lines 99b6d7a3ba1e
- 19d ago Changed · +5 lines 936b9f7e11e6
- 25d ago Changed · -28 lines cab2d0e58532
- 1mo ago Changed · +103 lines efe6462330cd
- 1mo ago Changed · +33 lines 40066d5936b5
- 1mo ago First seen · 257 lines · 13 tokens per session scan A aa93155d2c14
implement is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 3,710 once invoked, about $0.0001 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.
Other skills, from other repositories
gh
GitHub CLI skill for interacting with GitHub via the gh command line tool. Use when Bub needs to (1) Create, view, or manage GitHub repositories, (2) Work with issues and pull requests, (3) Create and manage releases, (4) Run and monitor GitHub Actions workflows, (5) Create and manage gists, (6) Install and manage…
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…
clawrium-release-announcements
Daily — draft a release blog post, open a PR, iterate on comments until merged.
blog-author
Watch ric03uec/clawrium release tags; draft a short blog post per user-visible feature as a PR against blog/.
release-watcher
Watch upstream Claw releases and clawrium discussions; surface top 3 feature candidates to Devashish via Discord DM for approve/skip.
repository-manager-development-lifecycle
The default entrypoint for one unit of work — plan, start, work with a live heartbeat, check, submit, watch status, and abort — composed entirely from the repository-manager MCP/CLI surface (rmlane, rmworktree, rmmergequeue, and rmconcepts). It never opens a raw shell, runs a direct compiler, hand-merges, or writes an…