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.svg" alt="Measured on agentmods" 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.02049 |
| Opus 5 | $0.00006 | $0.01025 |
| Sonnet 5 | $0.00003 | $0.00410 |
| Haiku 4.5 | $0.00001 | $0.00205 |
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 3d 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 — 257 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
Steps
Step 1: Analyze Issue (MANDATORY)
gh issue view <issue-number>
Extract:
- Issue title and description
- Labels (to determine branch prefix)
- Acceptance criteria
- Files to modify
Step 2: Determine Branch Name
Based on issue labels:
| Issue Label | Branch Prefix |
|---|---|
enhancement |
feature/ |
bug |
bugfix/ |
refactor |
refactor/ |
documentation |
docs/ |
| (no label) | feature/ |
Format: <prefix>/<issue-number>-<short-description>
Step 3: Create Feature Branch (MANDATORY)
# Verify not already on a feature branch for this issue
git branch --show-current
# If on develop or main, create new branch
git fetch origin
git checkout -b <branch-name> origin/develop
CRITICAL: This step cannot be skipped. If already on the correct feature branch, verify and continue.
Step 3.5: Implementation Planning (MANDATORY)
Spawn the Architect agent using the Opus model with the issue description and relevant existing code as context:
Agent({
subagent_type: "architect",
model: "opus",
prompt: <issue description> + <relevant existing code context>
})
Gather relevant existing code context by:
- Reading files listed in the issue's "Files to Update / Modify" section
- Reading adjacent modules or traits that the new code must implement or extend
- Running
git grepfor key symbols mentioned in the issue
The Architect agent produces an implementation plan covering:
| Plan Section | Content |
|---|---|
| Files to modify | Path + reason for each file |
| Files to create | Path + module role + which layer (domain / application / adapter / port) |
| Interface design | New traits, structs, enums with their signatures |
| Implementation order | Step-by-step sequence with rationale |
| Risk flags | Potential layer boundary violations, DDD concerns, edge cases |
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.
- 3d 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 (5 stars, last pushed yesterday), licensed MIT. It adds 13 tokens to every session and 2,049 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
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, or (6) Perform any GitHub…
jira-developer-integration
Git and developer workflow integration. TRIGGERS: 'generate branch name', 'create branch name', 'branch name for', 'write PR description', 'PR description for', 'link PR', 'link pull request', 'parse commit', 'extract issue from commit', 'smart commit', 'development panel'. Use for Git, GitHub, GitLab, Bitbucket…
metagit-projects
Ongoing workspace and project management for OpenClaw and Hermes agents. Use when starting work, organizing repos, or before creating a new project folder so existing metagit projects are reused instead of duplicated.
metagit-rewrite-campaign
Orchestrate a reference-implementation rewrite across source and target repos using campaigns, parity registry conventions, objectives, and subagent handoffs.
metagit-control-center
Use when running metagit as an MCP control center for multi-repo awareness, guarded sync, and operational knowledge across ongoing agent tasks.
metagit-sharing-state
Configure shared coordination state (objectives, handoffs, approvals, events) across multiple agents and machines via METAGITSTATEURL, optional DynamoDB / MongoDB DocumentStore backends, and the ops HTTP path. Use when Hermes subagents, CI runners, or humans must see the same objective queue without Syncthing JSON…