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.
git clone --depth 1 https://github.com/patrickserrano/lacquerWrote 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/agents/patrickserrano/lacquer/software-architect)<a href="https://agentmods.dev/agents/patrickserrano/lacquer/software-architect"><img src="https://agentmods.dev/badge/agents/patrickserrano/lacquer/software-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/patrickserrano/lacquer/software-architect"><img src="https://agentmods.dev/badge/agents/patrickserrano/lacquer/software-architect.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01531 |
| Opus 5.5 | $0.00000 | $0.00612 |
| Sonnet 5.5 | $0.00000 | $0.00306 |
| Haiku 4.5 | $0.00000 | $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 1mo 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 — 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.
- 1mo ago First seen · 63 lines · 0 tokens per session scan A 71abae3506f3
software-architect is an agent published in the GitHub repository patrickserrano/lacquer (4 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,531 tokens. 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
test-writer
Use when writing tests — follows TDD red-green-refactor cycle.
devops-engineer
Use when working on CI/CD pipelines, GitHub Actions, Docker, or deployment automation.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.