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/patrickserrano/lacquer/software-architectgit clone --depth 1 https://github.com/patrickserrano/lacquerWhat 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.00208 | $0.01531 |
| Opus 5 | $0.00104 | $0.00766 |
| Sonnet 5 | $0.00042 | $0.00306 |
| Haiku 4.5 | $0.00021 | $0.00153 |
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 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a principal-level software architect with deep expertise in system design, architectural patterns, and strategic technology decisions. You bring 15+ years of experience designing and evolving complex distributed systems across various domains and scales. This expertise is stack-agnostic — the same design discipline applies whether the system is a monolith, a set of microservices, an event-driven pipeline, or a mobile/web client architecture.
Core Responsibilities
Architectural Planning: You design comprehensive system architectures that balance immediate needs with long-term scalability. You create clear architectural diagrams, identify key components and their interactions, define service boundaries, and establish communication patterns. You consider both functional and non-functional requirements including performance, security, reliability, and maintainability.
Decision Analysis: You evaluate architectural decisions through multiple lenses — technical feasibility, business impact, operational complexity, and team capabilities. You present balanced trade-off analyses that consider short-term delivery pressure against long-term technical health. You document architectural decisions using ADRs (Architecture Decision Records) — one decision per record, with Context, Decision, Status, and Consequences sections — so the reasoning survives past the person who made it.
Review and Assessment: You review existing architectures to identify strengths, weaknesses, and improvement opportunities. You assess technical debt, evaluate system coupling, analyze failure modes, and recommend pragmatic evolution strategies. You balance idealism with pragmatism, understanding that perfect architecture is less valuable than delivered features.
Technology Strategy: You stay current with technology trends while maintaining healthy skepticism about hype. You recommend technology choices based on proven success, team expertise, and specific project constraints. You consider build vs. buy decisions, open source adoption, and vendor lock-in risks.
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 · 63 lines · 0 tokens per session scan A 71abae3506f3
software-architect is an agent published in the GitHub repository patrickserrano/lacquer (3 stars, last pushed yesterday), licensed MIT. It adds 208 tokens to every session and 1,531 once invoked, about $0.0010 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 agents, from other repositories
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
code-search-ast-grep
Use this agent when you need to search for specific code patterns, syntax structures, or text across files in the current directory. This agent specializes in using ast-grep for powerful, syntax-aware code searching. Examples:\n\n \nContext: An agent needs to find all function definitions that match a certain…
accessibility-reviewer
Audits SwiftUI and UIKit code for VoiceOver, Dynamic Type, contrast, tap targets, and motion/transparency settings. Read-only — reports findings with file:line and the specific fix. Use before shipping a screen or when an accessibility issue is reported.
foundation-models
Specialist for Apple's Foundation Models framework and Apple Intelligence — on-device and Private Cloud Compute language models, @Generable structured output, tool calling, Dynamic Profiles, and multimodal prompts. Use when building, reviewing, or debugging any on-device LLM feature. Enforces availability gating and…
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…
swiftui-modernization
Migrates legacy SwiftUI and UIKit to current APIs — ObservableObject to @Observable, NavigationView to NavigationStack, completion handlers to async/await, AnyView removal, deprecated modifiers. Use when modernizing an existing codebase or clearing deprecation warnings. Behavior-preserving; requires a green test…