project-workflow

A workflow for developing, testing, and maintaining a generated Python project using its recorded settings and uv, a Python project and package tool.

In plain words
What is it for?
Use it for feature work, bug fixes, dependency changes, documentation, configuration, and tests across Python libraries, command-line tools, APIs, and AI applications.
Why use it?
It gives code and configuration changes a consistent process while preserving the project’s structure, dependencies, tests, and existing user edits.

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/leynier/python-template/project-workflow
Any agent
npx skills add leynier/python-template --skill project-workflow
Clone the repo
git clone --depth 1 https://github.com/leynier/python-template

Made for: Claude Code, Codex.

Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 346 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.00058 $0.00346
Opus 5 $0.00029 $0.00173
Sonnet 5 $0.00012 $0.00069
Haiku 4.5 $0.00006 $0.00035

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

Security

Grade A, and why

project-workflow 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.

template/skills/project-workflow/SKILL.md · 26 lines

What it actually says

Project Workflow

Use the generated project as the source of truth for its enabled layers.

Workflow

  1. Read .copier-answers.yml, pyproject.toml, and readme.md before changing architecture or commands.
  2. Preserve the src layout, public entry points, Python version, dependency groups, and existing user changes.
  3. Add dependencies with uv add or uv add --group dev; do not hand-edit the lockfile.
  4. Keep secrets out of source control. Document required values in .env.example and load them through the generated settings layer when present.
  5. Add or update tests alongside behavior changes.
  6. Run uv sync --all-groups, uv run ruff check ., uv run ruff format --check ., and uv run pytest before delivery.
  7. If the project was created from a Git reference and needs upstream fixes, use copier update only from a clean worktree and review the resulting diff carefully.

Entry Points

  • For a library, verify imports and its public API.
  • For a CLI, run its generated console command and a representative option.
  • For an API or interface, start it locally and exercise the health or primary route.
  • For MCP, agents, RAG, inference, training, or deployment, use the additional generated skill when present.
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 · 26 lines · 58 tokens per session scan A 32b039ac4c2f

Subscribe to this mod's changes

project-workflow is a skill published in the GitHub repository leynier/python-template (37 stars, last pushed 4d ago), licensed MIT. It adds 58 tokens to every session and 346 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-30.

Related

Other skills, from other repositories

heaven-style

Standalone personal code-quality, architecture, documentation, graphical-interface, and project-management guide for TypeScript and Python repositories. Use when writing or reviewing code or docs, designing architecture or UI, refactoring, or aligning tests; apply repository policy first, then shared design philosophy…

Magolor/Blueprint · 63 tokens

datamodel-code-generator

Use this skill when the user wants Python data models, Pydantic models, dataclasses, TypedDicts, msgspec structs, or type-safe Python classes generated from OpenAPI, AsyncAPI, JSON Schema, GraphQL, JSON/YAML/CSV sample data, MCP tool schemas, Protocol Buffers, XML Schema, Apache Avro, or existing Python model objects.…

koxudaxi/datamodel-code-generator · 147 tokens

background-task

Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.

vstorm-co/full-stack-ai-agent-template · 62 tokens

frontend-feature

Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.

vstorm-co/full-stack-ai-agent-template · 64 tokens

rag-knowledge

Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…

vstorm-co/full-stack-ai-agent-template · 76 tokens

alembic-migration

Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.

vstorm-co/full-stack-ai-agent-template · 56 tokens