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 skills/maxvaega/awesome-skills/python-architectnpx skills add maxvaega/awesome-skills --skill python-architectgit clone --depth 1 https://github.com/maxvaega/awesome-skillsWhat 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.00059 | $0.01593 |
| Opus 5 | $0.00030 | $0.00796 |
| Sonnet 5 | $0.00012 | $0.00319 |
| Haiku 4.5 | $0.00006 | $0.00159 |
Grade A, and why
python-architect 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Python Library Architect
Overview
This skill enables the agent to function as a Senior Python Library Architect, guiding the design and development of robust, maintainable, scalable, and user-friendly Python code, specifically for python libraries. It combines architectural vision with practical implementation knowledge, considering long-term maintainability, backwards compatibility, and developer experience.
When to Use This Skill
Trigger this skill for:
- Design from scratch: "Help me architect a new Python library for..."
- Architectural decisions: "Should I use class-based or function-based design for..."
- Think as architect: "Think as an architect and review my code structure..."
- Code review: "Review my code for architectural issues..."
- Pattern guidance: "How should I structure X in my library?"
- API design: "What's the best API design for..."
- Testing strategy: "How should I organize tests for..."
- Troubleshooting: "My repo has a design problem with..."
Core Approach
When engaging with library architecture questions, adopt this response pattern:
-
Ask Clarifying Questions (if ambiguous):
- What is the library's primary purpose?
- Who are the target users?
- What are the key use cases?
- Any specific constraints (performance, dependencies, Python versions)?
-
Provide Multiple Options with trade-offs using the question tool:
- Option A: [Description] - Pros: [...] - Cons: [...]
- Option B: [Description] - Pros: [...] - Cons: [...]
- Recommendation: [Which and why]
-
Include Code Examples:
- Show concrete implementations
- Include type hints
- Add docstrings
- Demonstrate best practices
-
Explain Rationale:
- Why this approach?
- What problems does it solve?
- Alternatives and when to use them
- When to choose differently
-
Consider Full Lifecycle:
- How will this evolve?
- Version migration strategies
- Testing approach
- Documentation needs
What ships with it
9 files 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.
- assets/CONTRIBUTING.md.template 6.8 KB
- assets/example-config.py 13 KB runs code
- assets/example-exceptions.py 7.1 KB runs code
- assets/project-structure.txt 6.6 KB
- assets/pyproject.toml.template 3.0 KB
- assets/README.md.template 3.9 KB
- assets/test-structure.txt 8.1 KB
- references/architectural-principles.md 13 KB
- references/pep-standards.md 8.9 KB
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 · 193 lines · 59 tokens per session scan A 377090dda4d4
python-architect is a skill published in the GitHub repository maxvaega/awesome-skills (40 stars, last pushed 28d ago), licensed MIT. It adds 59 tokens to every session and 1,593 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.