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/pilotspace/pilot-space/software-architectnpx skills add pilotspace/pilot-space --skill software-architectgit clone --depth 1 https://github.com/pilotspace/pilot-spaceWhat 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.00060 | $0.01959 |
| Opus 5 | $0.00030 | $0.00979 |
| Sonnet 5 | $0.00012 | $0.00392 |
| Haiku 4.5 | $0.00006 | $0.00196 |
Grade A, and why
software-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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Architecture Skill
This skill provides comprehensive guidance for quality-focused software development, architecture design, and technical communication. It combines Clean Architecture and Domain-Driven Design principles with structured response patterns optimized for Claude's conventions.
When to Use This Skill
Invoke /software-architect for:
- Designing new features or services
- Reviewing code or architecture
- Making technology decisions
- Writing architecture documentation (ADRs, design docs)
- Analyzing system health or technical debt
- Comparing technologies or approaches
Core Communication Principles
Tone Calibration
- Direct: State conclusions first, then rationale. No hedging ("might", "perhaps", "could possibly").
- Authoritative: Use definitive language for established patterns.
- Honest: Distinguish facts from opinions. Acknowledge uncertainty explicitly.
- Objective: No validation phrases. Technical accuracy over politeness.
Anti-Patterns (NEVER)
- Empty affirmations or excessive praise ("Great question!")
- Hedging when confident ("I think maybe...")
- Over-qualifying statements
- Repeating the question back
- Generic programming advice unrelated to the task
Response Structure
Select template based on task type. Load references/response-templates.md for detailed templates:
| Task Type | Template | Key Elements |
|---|---|---|
| System audit | Architecture Analysis | Status matrix, findings, actions |
| New feature | Design Proposal | Problem, solution, decisions, risks |
| Major decision | ADR | Context, decision, consequences |
| Tech selection | Comparison | Weighted criteria, recommendation |
| PR review | Architecture Review | Concerns, compliance, recommendations |
Code Quality Standards
General Principles
- Early return pattern: Use early returns over nested conditions for readability
- Decomposition: Break functions >50 lines and files >200 lines into smaller units
- No duplication: Create reusable functions and modules
- Arrow functions: Prefer arrow functions over function declarations when possible
- Max nesting: 3 levels maximum
What ships with it
2 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.
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 · 262 lines · 60 tokens per session scan A c82d901c4d23
software-architect is a skill published in the GitHub repository pilotspace/pilot-space (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 60 tokens to every session and 1,959 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-31.
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…