A guide for creating GitHub Issues in a consistent format. GitHub Issues are records used to describe work such as features, bugs, and documentation changes.

Use it to gather requirements and write English issue titles, descriptions, labels, and comments using the repository's templates.

Incomplete or inconsistent issues are harder for people and coding agents to understand and implement. This guide requires the key context and technical details before drafting one.

How Taketo-Yoda/uv-sbom configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/Taketo-Yoda/uv-sbom/develop/.claude/skills/issue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/Taketo-Yoda/uv-sbom

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/issue/github.svg)](https://agentmods.dev/skills/taketo-yoda/uv-sbom/issue)

Your own site

<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/issue"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/issue/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/taketo-yoda/uv-sbom/issue"><img src="https://agentmods.dev/badge/skills/taketo-yoda/uv-sbom/issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 773 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00773
Opus 5	$0.00006	$0.00387
Sonnet 5	$0.00002	$0.00155
Haiku 4.5	$0.00001	$0.00077

Measured 5d ago against content hash 2b9e28110a55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

issue 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.

.claude/skills/issue/SKILL.md · 148 lines

How it starts

The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/issue - Issue Creation Skill

Create GitHub Issues with consistent formatting and sufficient technical detail for autonomous implementation.

Language Requirement

IMPORTANT: All GitHub Issues MUST be written in English.

Issue title: English
Issue body: English
Labels: English
Comments: English

Steps

1. Read Issue Guidelines (MANDATORY)

Before drafting any Issue content, read:

.claude/issue-guidelines.md — full Issue creation guidelines, templates, and quality checklist

This file contains the authoritative structure, Pre-Submission Verification checklist, and examples of good/bad Issues.

2. Gather Information

After reading the guidelines, gather the following information from the user:

Type: Feature, Bug, Documentation, Refactor, or other
Summary: Brief description of the task
Context: Why is this needed?
Technical Details: Implementation hints if available

2. Determine Issue Template

Based on the type, use the appropriate structure:

Feature Request

## Summary
[Brief description of the feature]

## Problem
[What problem does this solve?]

## Proposed Solution
[How should this be implemented?]

## Technical Implementation
[Technical details for autonomous implementation]
- Files to modify:
- New files to create:
- Dependencies:
- Architecture considerations:

## Acceptance Criteria
- [ ] [Specific, testable criterion]
- [ ] [Another criterion]
- [ ] Tests added
- [ ] Documentation updated (if applicable)

Bug Report

## Summary
[Brief description of the bug]

## Current Behavior
[What happens now?]

## Expected Behavior
[What should happen?]

## Steps to Reproduce
1. [Step 1]
2. [Step 2]
3. [Step 3]

## Technical Details
- Environment: [OS, Rust version, etc.]
- Error messages:
- Related files:

## Proposed Fix
[Technical approach to fix]

## Acceptance Criteria
- [ ] Bug is fixed
- [ ] Tests added to prevent regression
- [ ] No new warnings from clippy

Read the full file on GitHub · 148 lines

Changes

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 · 148 lines · 12 tokens per session scan A 2b9e28110a55

Subscribe to this mod's changes

issue is a skill published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 773 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.

Project management Python sbom sbom-generator sbom-tool uv

uv-docs

Astral uv 0.11.x — fast Python package and project manager in Rust. Projects, scripts, tools, Python versions, pip interface.

pledgeandgrow/pledge-skills · 34 tokens

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.

apache/airflow · 41 tokens

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.

MemPalace/mempalace · 67 tokens

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…

bubbuild/bub · 87 tokens

workspace

Dynamic multi-repo and monorepo awareness for Claude Code. Analyze workspace topology, track API contracts, and maintain cross-repo context.

alinaqi/maggy · 30 tokens

ticket-craft

Create Jira/Asana/Linear tickets optimized for Claude Code execution - AI-native ticket writing.

alinaqi/maggy · 22 tokens

uv-sbom: Skill for Claude Code