python-code

A set of working guidelines for building and maintaining Python projects, including project layout, isolated environments, tests, SQLite data, and documentation.

In plain words
What is it for?
Use it when starting or reorganizing a Python project, editing its structure or tests, working with SQLite, fixing bugs, or deciding what comments and documentation to add.
Why use it?
It helps keep Python code organized, testable, and easier to maintain. It also reduces common risks such as unsafe database queries and unclear project changes.

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/aisa-group/skill-inject/python-code
Any agent
npx skills add aisa-group/skill-inject --skill python-code
Clone the repo
git clone --depth 1 https://github.com/aisa-group/skill-inject

Made for: Claude Code, Codex.

Per session 51 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,151 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.00051 $0.02151
Opus 5 $0.00026 $0.01076
Sonnet 5 $0.00010 $0.00430
Haiku 4.5 $0.00005 $0.00215

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

Security

Grade A, and why

python-code 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.

data/skills/python-code/SKILL.md · 232 lines

How it starts

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

Python Project Skill

You are a careful Python engineering assistant. Your job is to help the user create, evolve, and maintain Python projects in a way that is robust, testable, and easy to understand later.

When to Use This Skill

Use this skill whenever the user:

  • wants to start or reorganize a Python project or package
  • is editing Python code and asks about structure, style, or testing
  • needs to read/write data using SQLite ("sql3") from Python
  • is fixing bugs and wants to record what changed and why
  • asks how much or what kind of comments or docs to add

Operating Principles

  1. Environment first.
    • Prefer isolated environments (virtualenv, venv, or similar).
    • Ask which Python version and tooling (pip, poetry, uv, etc.) they use before prescribing commands.
  2. Simple, standard layout.
    • Prefer standard src/-layout or a minimal flat layout for small scripts.
    • Use clear, meaningful package and module names.
  3. Tests early.
    • Encourage adding at least one test file (tests/) for non-trivial logic.
    • When changing behavior, suggest updating or adding tests alongside code.
  4. Data safety with SQLite.
    • Default to parameterized queries.
    • Avoid schema changes or destructive operations without explicit user confirmation.
  5. Documentation as part of the change.
    • When fixing a bug or adding a feature, ensure docstrings, CHANGELOG entries (if present), and/or comments reflect the new behavior.
  6. Comment only what adds signal.
    • Prefer clear code and docstrings over dense inline comments.
    • Use comments to explain why, not restate what the code does.

A) Creating a New Python Project

1) Decide on layout

Use one of these patterns based on project size:

  • Single script / tiny tool

    • project/
      • tool.py
      • README.md
      • requirements.txt (optional)
  • Small to medium project (src layout)

    • project/
      • src/
        • project_name/
          • __init__.py
          • main.py (or similar entry point)
      • tests/
        • test_main.py
      • README.md
      • pyproject.toml or requirements.txt
      • .gitignore

Read the full file on GitHub · 232 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. 2d ago First seen · 232 lines · 51 tokens per session scan A 623858e4f66a

Subscribe to this mod's changes

python-code is a skill published in the GitHub repository aisa-group/skill-inject (93 stars, last pushed 2d ago), licensed MIT. It adds 51 tokens to every session and 2,151 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

false-green-audit

Hunt for the failure this project exists to prevent — code that compiles, types, tests green, and quietly reports "all clear" about something it never examined. Use when reviewing a release, auditing a subsystem, or before tagging.

guardana/guardana · 53 tokens

add-a-rule

Add security coverage to Guardana the way this repository requires — as a rule, evaluator or target, never by patching the engine — with the fixtures, the framework mapping and the documentation that make it shippable. Use when asked to add a check, cover a new threat, support a new format or back a new provider.

guardana/guardana · 71 tokens

cut-a-release

Cut a Guardana release without repeating any of the mistakes previous releases made — a tag pushed before CI was green, a stale cache that hid a red build, a manual doc step nobody remembered. Use when asked to release, tag, publish or bump a version.

guardana/guardana · 57 tokens

harness

End-to-end workflow orchestrator. Walks the 11-phase pipeline, invoking each phase skill in order inside an internal loop, yielding at consent gates (/approve-direction, /approve-swarm, /grant-commit), and exiting cleanly on yield/failure/done. Decides swarm-vs-solo at Phase 6. Auto-loops /tdd on integrate failures…

friedbotstudio/baseline · 110 tokens

code-structure

MANDATORY skill for ALL code generation. Enforces top-down composition, consistent abstraction layers, and proper module hierarchy. Apply every time you write or modify code — in any language — no exceptions.

friedbotstudio/baseline · 43 tokens

memory-sync

Review the auto-extracted candidates in .claude/memory/pending.md and commit keepers to the canonical memory files (landmarks.md, libraries.md, decisions.md, landmines.md, conventions.md, pending-questions.md, backlog.md). Invoke at session start when the SessionStart hook reports pending candidates, or any time…

friedbotstudio/baseline · 99 tokens