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/split/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/split)<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/split"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/split.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.1 | $0.00032 | $0.01128 |
| Opus 5 | $0.00016 | $0.00564 |
| Sonnet 5 | $0.00006 | $0.00226 |
| Haiku 4.5 | $0.00003 | $0.00113 |
Grade A, and why
split 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 2d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/split - Issue Decomposition Skill
Decomposes a large GitHub Issue into subtask Issues, each implementable autonomously in a single PR.
Language Requirement
IMPORTANT: All created GitHub Issues MUST be written in English.
Workflow Overview
Read Parent Issue → Propose Decomposition → Wait for Confirmation → Create Subtask Issues → Comment on Parent
Steps
Step 1: Read the Parent Issue (MANDATORY)
gh issue view <issue-number>
Extract:
- Issue title and overall scope
- Acceptance criteria
- Files to modify
- Any existing dependencies or constraints
Step 2: Analyze and Propose Decomposition
Identify subtask boundaries using these dimensions:
| Dimension | Example |
|---|---|
| Module boundary | Changes touch independent modules (e.g., adapters/ vs domain/) |
| Concern boundary | "add struct" vs "add tests" vs "update CLI flag" |
| Sequential dependency | Subtask B requires subtask A to merge first |
| Risk boundary | Mechanical rename vs logic change should be separate |
Granularity rule: Each subtask must be implementable in a single focused PR.
Guard rails:
- If the issue is already small enough for one PR → report "No split needed. This issue is already scoped for a single PR." Do NOT create any subtask Issues.
- If decomposition yields more than 7 subtasks → flag over-decomposition and suggest grouping before proceeding.
- Line-count target: Aim for ≤ 200 changed lines per subtask PR. If a subtask is estimated to exceed this, consider splitting it further. This is a guideline, not a hard limit.
Present the proposed subtasks to the user in this format:
Proposed split for #<parent>:
1. [Short title] — [one-line rationale]
2. [Short title] — [one-line rationale]
...
Dependencies:
- #2 depends on #1 (reason)
Proceed? (yes / adjust / cancel)
Step 3: Wait for Explicit Confirmation
Do NOT create any Issues until the user explicitly confirms.
Accepted responses: "yes", "proceed", "go ahead", or equivalent affirmation. If the user asks for adjustments, revise the proposal and present again. If the user cancels, stop and report "Split cancelled."
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.
- 2d ago First seen · 170 lines · 32 tokens per session scan A 78b9febc86d3
split is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (5 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,128 once invoked, about $0.0002 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
uv-docs
Astral uv 0.11.x — fast Python package and project manager in Rust. Projects, scripts, tools, Python versions, pip interface.
aip-tracker
Track Airflow Improvement Proposal (AIP) implementation progress by comparing Confluence specs against codebase evidence. Use when asked to assess, report on, or compare AIP status.
mempalace-task
Create, hand off, claim, execute, and close agent tasks through the MemPalace logstream. Use when the user wants to delegate work, prepare a ready-to-paste task for another agent, receive a MemPalace task id, or explicitly launch a supported headless agent in controlled mode.
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…
auditing-endpoints
Audit every endpoint in a PostHog project for staleness, failed materialisations, and unused materialised versions. Use when the user asks "what endpoints can I clean up?", "are any of my endpoints broken?", "which materialised versions are still being called?", or wants a one-shot cleanup pass over the Endpoints…
managing-endpoint-versions
Work safely with endpoint versions — preview a draft in the playground, roll back to an older version, update settings on one version without bumping query history, deactivate a specific version. Use when the user asks "how do I roll back my endpoint", "preview my changes before publishing", "I want to fix v5 without…