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.
npx agentmods add commands/dmitriyyukhanov/claude-plugins/python-devgit clone --depth 1 https://github.com/DmitriyYukhanov/claude-pluginsWhat 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.00017 | $0.00540 |
| Opus 5 | $0.00009 | $0.00270 |
| Sonnet 5 | $0.00003 | $0.00108 |
| Haiku 4.5 | $0.00002 | $0.00054 |
Grade A, and why
python-dev 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Development Workflow
You are orchestrating a complete Python development workflow. Follow these phases systematically.
Phase 1: Discovery
First, understand the project and task:
-
Check for Python project markers:
pyproject.tomlrequirements.txtorPipfilesetup.pyorsetup.cfg.pyfiles- Framework config (FastAPI, Django, Flask)
-
Read existing architecture:
- Check for
CLAUDE.mdor project documentation - Look at existing code patterns in
src/ - Identify framework and dependencies
- Check for
-
Clarify requirements if task is ambiguous using AskUserQuestion
Phase 2: Architecture
Use the python-architect skill knowledge to:
- Design module structure - Protocols, package hierarchy
- Create test stubs - pytest test cases
- Generate Mermaid diagrams - Class, data flow diagrams
- Define contracts - Protocols/ABCs before implementations
Present the architecture to the user for approval before implementing.
Phase 3: Implementation
Use the python-coder skill knowledge to implement:
- Follow PEP 8 and project conventions precisely
- Implement against the test stubs created in Phase 2
- Run tests continuously as you implement
- Use type hints everywhere
Phase 4: Review
Spawn the python-reviewer agent to perform Python-specific code review:
- Type hint coverage
- PEP 8 compliance
- Error handling patterns
- Async correctness
- Performance concerns
Phase 5: Testing
Use the python-testing skill knowledge to:
- Ensure unit tests pass
- Ensure integration tests pass
- Generate coverage report for critical paths if requested
Workflow Commands
You can run individual phases:
- "architect only" - Just Phase 2
- "implement only" - Just Phase 3 (requires existing architecture)
- "review only" - Just Phase 4
- "test only" - Just Phase 5
Usage Examples
/python-dev Add REST API with FastAPI
/python-dev Implement data processing pipeline
/python-dev Create CLI tool with Click
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 · 86 lines · 17 tokens per session scan A 9d256f6d2010
python-dev is a command published in the GitHub repository DmitriyYukhanov/claude-plugins (7 stars, last pushed 2d ago), licensed MIT. It adds 17 tokens to every session and 540 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.
Other commands, from other repositories
plan-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results.
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
build
Guided feature development with approval gates at each phase.
release
Generate changelog, bump version, and create git tag.
feature-flow-w
Complete git worktree workflow orchestration (GitHub/GitLab/Forgejo) - worktree, branch, issue, commit.
bootstrap
Scaffold test, lint, and CI infrastructure for projects that lack it.