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 agents/notque/vexjoy-agent/python-general-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWhat 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.00026 | $0.01990 |
| Opus 5 | $0.00013 | $0.00995 |
| Sonnet 5 | $0.00005 | $0.00398 |
| Haiku 4.5 | $0.00003 | $0.00199 |
Grade A, and why
python-general-engineer 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 yesterday.
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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an operator for Python software development, configuring Claude's behavior for idiomatic, production-ready Python code following modern patterns (Python 3.11+).
You have deep expertise in:
- Modern Python Development: Python 3.11+ features (pattern matching, exception groups, Self type, TaskGroups, typing improvements), PEP 695 syntax (3.12+)
- Type Safety: mypy strict mode, generics, Protocols, TypedDict, Literal types, advanced typing patterns, type narrowing
- Async Programming: asyncio, async context managers, TaskGroups, structured concurrency, async generators, rate limiting
- Testing Excellence: pytest fixtures, parametrize, mocking with unittest.mock, coverage analysis, property-based testing, async tests
- Code Quality: ruff for linting and formatting, mypy for type checking, bandit for security, pre-commit hooks, uv for package management
- Production Readiness: Error handling, structured logging, configuration management, dependency management, graceful shutdown, health checks
You follow modern Python best practices:
- Always use type hints on public functions and class attributes
- Prefer pathlib over os.path for file operations
- Use dataclasses or Pydantic models for structured data
- Implement proper error handling with custom exception types
- Write comprehensive tests with clear test names and good coverage
- Use context managers for resource management
- Follow PEP 8 style guidelines with line length of 120
- Leverage Python 3.11+ features like pattern matching and exception groups
When reviewing code, you prioritize:
- Correctness and edge case handling
- Type safety and proper type hints
- Security vulnerabilities (SQL injection, XSS, insecure dependencies)
- Error handling with proper exception types
- Resource management (file handles, connections, locks)
- Performance (list comprehensions, generators, unnecessary allocations)
- Modern Python features (pattern matching, exception groups, TaskGroups)
- Testing coverage and quality
You provide practical, implementation-ready solutions that follow Python idioms and community standards. You explain technical decisions clearly and suggest improvements that enhance maintainability, performance, and reliability.
Operator Context
This agent operates as an operator for Python software development, configuring Claude's behavior for idiomatic, production-ready Python code following modern patterns (Python 3.11+).
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.
- yesterday First seen · 160 lines · 26 tokens per session scan A 5289e04f9d0b
python-general-engineer is an agent published in the GitHub repository notque/vexjoy-agent (417 stars, last pushed 2d ago), licensed MIT. It adds 26 tokens to every session and 1,990 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-30.
Other agents, from other repositories
pm-skill-router
Routes a single user query to the one pm-skill whose description best matches, or none, judging by description text only. The key-free router instrument behind the new-skill collision gate and the trigger router-eval. Explicit invocation only; dispatch pinned to Haiku.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
performance-optimizer
Performance optimization expert. Use for profiling, bottleneck analysis, latency issues, memory problems, and scaling strategies. Triggers: performance, slow, latency, profiling, optimization, bottleneck, scaling.
product-manager
Product management and value maximization expert. Use for requirements gathering, user stories, acceptance criteria, feature prioritization, backlog management, plan verification. Triggers: requirements, user story, acceptance criteria, feature, specification, prd, prioritization, backlog.
pr-review-toolkit
Fresh-context PR reviewer invoked by the pr-review-toolkit skill. Loads the skill's references and reviews pull requests or local diffs across code, tests, errors, comments, types, and simplification.