essentials: Command for Claude Code

.cursor/commands/create-python-package.md

create-python-package is a command for Claude Code, Cursor from CiscoDevNet/essentials. It costs 0 tokens per session (546 once invoked), scanned A, original, Apache-2.0.

A command for creating a new Python package with uv, a Python project and dependency manager, in a chosen directory. It adds the package to the workspace configuration and uses the Hatchling build system.

In plain words
What is it for?
It helps start a Python library in a specified location and add it to the root project's workspace members.
Why use it?
It removes the repetitive setup work involved in creating package files, naming the directory, and registering the package in a multi-package workspace.

Command for Claude CodeCursor

Written for Cursor and Claude Code: installed under .cursor/, but also a Claude Code command (commands/*.md).

This is CiscoDevNet/essentials's own configuration. It tells Claude Code and Cursor how to work on essentials itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything essentials configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CiscoDevNet/essentials. 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/CiscoDevNet/essentials/main/.cursor/commands/create-python-package.md
Clone the repo
git clone --depth 1 https://github.com/CiscoDevNet/essentials

Made for: Claude Code, Cursor.

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 create-python-package

README.md
[![agentmods](https://agentmods.dev/badge/commands/ciscodevnet/essentials/create-python-package/github.svg)](https://agentmods.dev/commands/ciscodevnet/essentials/create-python-package)
Your own site
<a href="https://agentmods.dev/commands/ciscodevnet/essentials/create-python-package"><img src="https://agentmods.dev/badge/commands/ciscodevnet/essentials/create-python-package/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 create-python-package

Your own site · 80×15
<a href="https://agentmods.dev/commands/ciscodevnet/essentials/create-python-package"><img src="https://agentmods.dev/badge/commands/ciscodevnet/essentials/create-python-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 546 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00546
Opus 5.5 $0.00000 $0.00218
Sonnet 5.5 $0.00000 $0.00109
Haiku 4.5 $0.00000 $0.00055

Measured 1mo ago against content hash 1ec182b721b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-python-package 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 1mo 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.

.cursor/commands/create-python-package.md · 55 lines

How it starts

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

Create a new Python package using uv in the specified directory.

Parameters

  • directory_location: The directory path where the new package should be created
  • package_name: The name of the Python package to create

Behavior

  1. If directory_location is not provided, ask the user: "What directory should the package be created in?"
  2. If package_name is not provided, ask the user: "What should the package be named?"
  3. Navigate to the specified directory location (create it if it doesn't exist)
  4. Run uv init --lib <package_name> in that directory
  5. Add the new package to the project's root pyproject.toml file in the [tool.uv.workspace] members list (create the section if it doesn't exist)
  6. The entry should use the format: "<relative_path_from_root>/<package_name>"
    • Convert underscores in package_name to hyphens for the directory name (e.g., my_new_package becomes my-new-package)
    • The path should be relative to the workspace root (e.g., if directory_location is tools/python and package_name is my_new_package, the path would be tools/python/my-new-package)
  7. Ensure the new package uses hatchling as the build backend:
    [build-system]
    requires = ["hatchling"]
    build-backend = "hatchling.build"
    
  8. Confirm the package was created successfully and added to the root pyproject.toml

Example Usage

With parameters:

  • directory_location: tools/python
  • package_name: my_new_package
  • This will create the package at tools/python/my-new-package/ and add to root pyproject.toml:
    [tool.uv.workspace]
    members = [
        "tools/python/core_github",
        "tools/python/gcp_gemini",
        "tools/python/my-new-package",
    ]
    

Without parameters:

  • Prompt user for directory location
  • Prompt user for package name
  • Then proceed with creation

Notes

  • The directory location can be absolute or relative to the workspace root
  • If the directory doesn't exist, create it before running uv init
  • The package name should follow Python naming conventions (lowercase, underscores allowed)
  • The directory name in the workspace members list should use hyphens (e.g., my-new-package)
  • If [tool.uv.workspace] section doesn't exist in the root pyproject.toml, create it before adding the new package

Read the full file on GitHub · 55 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. 1mo ago First seen · 55 lines · 0 tokens per session scan A 1ec182b721b8

Subscribe to this mod's changes

create-python-package is a command published in the GitHub repository CiscoDevNet/essentials (7 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 546 tokens. 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.