python-packaging

python-packaging is a skill for Claude Code from HermeticOrmus/LibreUIUX-Claude-Code. It costs 43 tokens per session (4,927 once invoked), scanned C, original, MIT.

A guide to packaging Python code so it can be installed, built, and distributed. It covers project structure, package metadata, build systems, wheels, source archives, and publishing to PyPI, the Python package index.

In plain words
What is it for?
Use it to create Python libraries or command-line tools, configure `pyproject.toml`, build distribution files, manage dependencies, and publish packages.
Why use it?
It helps turn Python source code into a consistent installable distribution and avoids missing or unclear package configuration.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is path: ./wheelhouse/*.whl.

Part of the python-development plugin — 3 skills shipped together

Good fit Use it to create Python libraries or command-line tools, configure pyproject.toml, build distribution files, manage dependencies, and publish packages.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/HermeticOrmus/LibreUIUX-Claude-Code
agentmods
npx agentmods add skills/hermeticormus/libreuiux-claude-code/python-packaging

Made for: Claude Code.

Or install python-development, the plugin that ships this one along with the rest of its 3 skills.

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.

agentmods badge for python-packaging

README.md
[![agentmods](https://agentmods.dev/badge/skills/hermeticormus/libreuiux-claude-code/python-packaging/github.svg)](https://agentmods.dev/skills/hermeticormus/libreuiux-claude-code/python-packaging)
Your own site
<a href="https://agentmods.dev/skills/hermeticormus/libreuiux-claude-code/python-packaging"><img src="https://agentmods.dev/badge/skills/hermeticormus/libreuiux-claude-code/python-packaging/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.

agentmods 80×15 button for python-packaging

Your own site · 80×15
<a href="https://agentmods.dev/skills/hermeticormus/libreuiux-claude-code/python-packaging"><img src="https://agentmods.dev/badge/skills/hermeticormus/libreuiux-claude-code/python-packaging.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,927 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00043 $0.04927
Opus 5.5 $0.00017 $0.01971
Sonnet 5.5 $0.00009 $0.00985
Haiku 4.5 $0.00004 $0.00493

Measured 26d ago against content hash 58082e4b1e32, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

python-packaging scanned grade C with 1 finding 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 26d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf test-env
plugins/python-development/skills/python-packaging/SKILL.md · 871 lines

How it starts

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

Python Packaging

Comprehensive guide to creating, structuring, and distributing Python packages using modern packaging tools, pyproject.toml, and publishing to PyPI.

When to Use This Skill

  • Creating Python libraries for distribution
  • Building command-line tools with entry points
  • Publishing packages to PyPI or private repositories
  • Setting up Python project structure
  • Creating installable packages with dependencies
  • Building wheels and source distributions
  • Versioning and releasing Python packages
  • Creating namespace packages
  • Implementing package metadata and classifiers

Core Concepts

1. Package Structure

  • Source layout: src/package_name/ (recommended)
  • Flat layout: package_name/ (simpler but less flexible)
  • Package metadata: pyproject.toml, setup.py, or setup.cfg
  • Distribution formats: wheel (.whl) and source distribution (.tar.gz)

2. Modern Packaging Standards

  • PEP 517/518: Build system requirements
  • PEP 621: Metadata in pyproject.toml
  • PEP 660: Editable installs
  • pyproject.toml: Single source of configuration

3. Build Backends

  • setuptools: Traditional, widely used
  • hatchling: Modern, opinionated
  • flit: Lightweight, for pure Python
  • poetry: Dependency management + packaging

4. Distribution

  • PyPI: Python Package Index (public)
  • TestPyPI: Testing before production
  • Private repositories: JFrog, AWS CodeArtifact, etc.

Quick Start

Minimal Package Structure

my-package/
├── pyproject.toml
├── README.md
├── LICENSE
├── src/
│   └── my_package/
│       ├── __init__.py
│       └── module.py
└── tests/
    └── test_module.py

Minimal pyproject.toml

[build-system]
requires = ["setuptools>=61.0"]
build-backend = "setuptools.build_meta"

[project]
name = "my-package"
version = "0.1.0"
description = "A short description"
authors = [{name = "Your Name", email = "[email protected]"}]
readme = "README.md"
requires-python = ">=3.8"
dependencies = [
    "requests>=2.28.0",
]

[project.optional-dependencies]
dev = [
    "pytest>=7.0",
    "black>=22.0",
]

Read the full file on GitHub · 871 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.

  1. 26d ago First seen · 871 lines · 43 tokens per session scan C 58082e4b1e32

Subscribe to this mod's changes

python-packaging is a skill published in the GitHub repository HermeticOrmus/LibreUIUX-Claude-Code (115 stars, last pushed 11d ago), licensed MIT. It adds 43 tokens to every session and 4,927 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-20.