build-python-apps

Guidance for building Python applications and packages with a consistent project layout, dependency management, type annotations, checks, and tests.

In plain words
What is it for?
Use it for Python services, libraries, uv projects, business-logic layers, configuration, dependencies, API schemas, and pytest-based tests.
Why use it?
It reduces confusion about where code belongs and helps catch formatting, typing, and behavior problems during development.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/lordsarcastic/skills/build-python-apps
Any agent
npx skills add lordsarcastic/skills --skill build-python-apps
Clone the repo
git clone --depth 1 https://github.com/lordsarcastic/skills

Made for: Claude Code, Codex.

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 663 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00056 $0.00663
Opus 5 $0.00028 $0.00331
Sonnet 5 $0.00011 $0.00133
Haiku 4.5 $0.00006 $0.00066

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

Security

Grade A, and why

build-python-apps 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.

build-python-apps/SKILL.md · 82 lines

How it starts

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

Build Python Apps

Core Defaults

Use Python 3.12 or newer unless the existing project pins another version. Prefer uv for dependency management, pyproject.toml for project configuration, Ruff for linting/formatting, Pyright in basic mode for type checking, and pytest for tests.

Write typed Python. Add parameter and return annotations for new functions and methods. Keep dynamic or loosely typed code at dependency boundaries, not in core logic.

Structure

Use src layout for applications and libraries:

src/
└── package_name/
    ├── __init__.py
    ├── config/
    ├── services/
    ├── libs/
    ├── models/
    ├── schemas/
    ├── types/
    └── utils/
tests/

Use boundaries consistently:

  • services: business logic, workflows, orchestration, validation that is not framework-specific, and use cases.
  • libs: integrations with external dependencies such as Redis, HTTP clients, Sentry, OpenTelemetry, storage, queues, auth clients, and database setup.
  • models: persistence or domain models.
  • schemas: Pydantic or API/data-transfer schemas.
  • types: shared protocols, enums, and type aliases.
  • utils: small generic helpers only; move anything domain-specific into services.

Do not put business rules in scripts, CLIs, HTTP handlers, or serializers when a service layer exists.

Style

Follow PEP 8 and the repo's Ruff settings. Prefer line length 79 when creating new Python configs unless an existing project specifies otherwise.

Import style:

  • Keep imports sorted with Ruff.
  • Break imports involving more than three names into parenthesized multi-line imports.
  • Avoid star imports except in existing settings modules where the project already uses them intentionally.

Prefer explicit exceptions and structured error payloads at boundaries. Keep secrets and tokens out of logs.

Configuration And Dependencies

Use pyproject.toml for:

  • [project] metadata and runtime dependencies.
  • [dependency-groups].dev for Ruff, Pyright, pytest, pytest plugins, and factories.
  • [tool.ruff], [tool.pyright], and [tool.pytest.ini_options].

Read the full file on GitHub · 82 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 82 lines · 56 tokens per session scan A b8bab308d9c0

Subscribe to this mod's changes

build-python-apps is a skill published in the GitHub repository lordsarcastic/skills (10 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 663 once invoked, about $0.0003 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-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens