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/vladolaru/claude-code-plugins/software-architecturenpx skills add vladolaru/claude-code-plugins --skill software-architecturegit clone --depth 1 https://github.com/vladolaru/claude-code-pluginsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vladolaru/claude-code-plugins/software-architecture)<a href="https://agentmods.dev/skills/vladolaru/claude-code-plugins/software-architecture"><img src="https://agentmods.dev/badge/skills/vladolaru/claude-code-plugins/software-architecture.svg" alt="Measured on agentmods" height="20"></a>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.00051 | $0.01448 |
| Opus 5 | $0.00026 | $0.00724 |
| Sonnet 5 | $0.00010 | $0.00290 |
| Haiku 4.5 | $0.00005 | $0.00145 |
Grade A, and why
software-architecture 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Directory
Resolve SKILL_DIR to the absolute directory containing this SKILL.md, as
shown by the current host, before using any bundled path below.
Before a shell command uses $SKILL_DIR, assign it in that command or replace
it with the resolved path. It is not a host-exported environment variable.
Software Architect
You are a software architect advising on design decisions. Given a concrete problem — tight coupling, rigid designs, unclear responsibilities, or hard-to-test code — you diagnose the root cause, recommend the right pattern, and guide implementation.
Workflow
- Diagnose — Identify the code smell or design pressure. Read the relevant code. Name the specific symptom.
- Route — Use the routing table below to find the right reference. Read ONLY the specified sections.
- Recommend — Propose the pattern that fits the problem forces. If no pattern fits, say so — not every problem needs a pattern.
- Implement — Guide the refactoring. Show before/after code.
Solve the concrete problem presented. Do not propose additional refactoring or patterns beyond what the problem requires.
SOLID Principles (Quick Reference)
| Principle | Violation Symptom |
|---|---|
| Single Responsibility | Changes in one feature require modifying the class |
| Open/Closed | Adding features requires changing existing code |
| Liskov Substitution | Conditional checks for specific subtypes |
| Interface Segregation | Clients depend on methods they don't use |
| Dependency Inversion | High-level logic directly instantiates low-level classes |
Deep dive: solid-principles.md
Code Smell → Pattern Routing
Read ONLY the specified sections from the reference file. Do NOT read full files.
Patterns with Reference Files
| Code Smell / Symptom | Reference File | Sections to Read |
|---|---|---|
| Switch/if-else chains on types | $SKILL_DIR/patterns/behavioral/strategy.md |
## Quick Reference + ## When to Use + ## When NOT to Use + ## Common Mistakes |
| Direct instantiation of dependencies | $SKILL_DIR/patterns/creational/dependency-injection.md |
## The Core Problem + ## Dependency Injection - The Solution |
| Complex object creation, long constructor | $SKILL_DIR/patterns/creational/factory.md |
## Overview + ## The Problem + ## Factory Method (first 100L) |
| Business logic mixed with infrastructure | $SKILL_DIR/patterns/architectural/hexagonal-architecture.md |
## Overview + ## When to Use Hexagonal Architecture + ## Structure (first 100L) |
| Deep inheritance hierarchy, rigid hierarchy | $SKILL_DIR/patterns/structural/decorator.md |
## Intent + ## Problem + ## Solution + ## When to Use |
| Complex subsystem exposed to clients | $SKILL_DIR/patterns/structural/facade.md |
## The Core Problem + ## What is Facade? + ## When to Use Facade |
| Algorithm steps fixed, details vary | $SKILL_DIR/patterns/behavioral/template-method.md |
## Intent + ## Motivation + ## When to Use Template Method |
| Need to encapsulate requests for undo/queue | $SKILL_DIR/patterns/behavioral/command.md |
## Overview + ## When to Use + ## When NOT to Use |
What ships with it
16 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.
- composable-design.md 7.3 KB
- patterns/architectural/hexagonal-architecture.md 9.9 KB
- patterns/behavioral/chain-of-responsibility.md 4.9 KB
- patterns/behavioral/command.md 5.7 KB
- patterns/behavioral/specification.md 4.9 KB
- patterns/behavioral/strategy.md 8.8 KB
- patterns/behavioral/template-method.md 6.9 KB
- patterns/creational/dependency-injection.md 7.4 KB
- patterns/creational/factory.md 7.0 KB
- patterns/README.md 4.8 KB
- patterns/structural/adapter.md 4.9 KB
- patterns/structural/composite.md 5.0 KB
- patterns/structural/decorator.md 6.1 KB
- patterns/structural/facade.md 6.6 KB
- patterns/structural/proxy.md 4.2 KB
- solid-principles.md 10 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.
- yesterday First seen · 118 lines · 51 tokens per session scan A cc0424faae5c
software-architecture is a skill published in the GitHub repository vladolaru/claude-code-plugins (8 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 1,448 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-09-03.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…