What is py-structure?

A Python project-structure review command that examines how files, modules, and application layers are organized. It checks approaches such as layered and hexagonal architecture, where core business code is kept separate from outside systems.

Use it to map a Python backend, find files that should be split, check layer dependencies, and get recommendations for organizing modules and core components.

It helps reveal oversized files, tangled imports, misplaced dependencies, and missing boundaries before the project becomes harder to change.

py-structure — Command by mathisk2095

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 commands/mathisk2095/jko-claude-plugins/py-structure

Clone the repo

git clone --depth 1 https://github.com/mathisk2095/jko-claude-plugins

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 416 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.

Model	Per session	Once invoked
Fable 5	$0.00023	$0.00416
Opus 5	$0.00012	$0.00208
Sonnet 5	$0.00005	$0.00083
Haiku 4.5	$0.00002	$0.00042

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

Security

Grade A, and why

py-structure 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.

plugins/python-backend/commands/py-structure.md · 56 lines

What it actually says

Analyze the Python backend project structure and recommend improvements. If $ARGUMENTS is provided, analyze that directory. Otherwise auto-detect src/ or backend/.

First: Use the python-backend-expert skill. Read references/project-structure.md and references/architecture.md.

Analysis Steps

Map the project:
- List all Python files with line counts
- Identify the architectural pattern (hexagonal, layered, flat, feature-based)
- Detect framework (Litestar/FastAPI)
File size audit:
- Flag files >300 lines (candidate for split)
- Flag files >500 lines (must split)
- For each oversized file, suggest specific split strategy
Layer boundary check:
- Verify domain has no infrastructure imports
- Verify entrypoints don't import from infrastructure directly (except through DI)
- Check for circular import risks
Module organization check:
- One major class per file?
- Logical grouping by domain?
- Proper __init__.py re-exports?
- Import order following convention?
Missing components:
- Missing domain entities (using ORM models directly)?
- Missing ports/protocols?
- Missing service layer?
- Missing exception hierarchy?

Output

Current Structure

Tree view with line counts and layer annotations.

Structure Score: X/10

Issues Found

Ordered by impact, with specific file moves/splits/creates recommended.

Recommended Structure

If the current structure needs major changes, show the ideal target layout.

Migration Steps

If restructuring is needed, provide step-by-step plan that keeps the app working at each step.

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.

2d ago First seen · 56 lines · 23 tokens per session scan A d549af36790a

Subscribe to this mod's changes

py-structure is a command published in the GitHub repository mathisk2095/jko-claude-plugins (3 stars, last pushed 4d ago), licensed MIT. It adds 23 tokens to every session and 416 once invoked, about $0.0001 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.

Backend and APIs Code review Planning ai-coding claude-code claude-code-marketplace claude-code-plugin claude-code-skills

py-structure

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Analysis Steps

Output

Current Structure

Structure Score: X/10

Issues Found

Recommended Structure

Migration Steps

What this file has done since we first saw it

Other commands, from other repositories

status

codex-review

stats

close

prompt

submit