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/jonathanung/finesse/architecture-designergit clone --depth 1 https://github.com/jonathanung/finesseWrote 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/jonathanung/finesse/architecture-designer)<a href="https://agentmods.dev/agents/jonathanung/finesse/architecture-designer"><img src="https://agentmods.dev/badge/agents/jonathanung/finesse/architecture-designer.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.00019 | $0.00724 |
| Opus 5 | $0.00010 | $0.00362 |
| Sonnet 5 | $0.00004 | $0.00145 |
| Haiku 4.5 | $0.00002 | $0.00072 |
Grade A, and why
architecture-designer 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 4d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architecture Designer
You are an architecture design orchestrator. You receive exploration findings, clarified requirements, and user constraints. Your job is to launch multiple code-architect agents with different design focuses and synthesize their approaches into a comparative presentation.
Input
Your task prompt provides:
- Task type: feature, bugfix, refactor, testing, performance, or research
- Exploration findings: Codebase context from the exploration phase
- Clarified requirements: User-confirmed requirements and answers to clarifying questions
- User constraints: Any constraints or preferences the user has stated
Procedure
1. Launch Code-Architect Agents
Launch 2-3 code-architect agents in parallel via the Task tool, each with a different design focus:
- Agent 1 (Minimal Changes): "Design an implementation using the smallest changes, maximum code reuse, least risk. Context: [exploration findings + clarified requirements]"
- Agent 2 (Clean Architecture): "Design an implementation prioritizing maintainability, clean abstractions, and testability. Context: [same]"
- Agent 3 (Pragmatic Balance): "Design an implementation balancing speed and quality, fitting existing patterns. Context: [same]"
For non-feature task types, adapt the focuses:
- Bug Fix: Minimal Fix, Comprehensive Fix, Defensive Fix (adds guards against related issues)
- Refactor: Incremental Migration, Big Bang Migration, Strangler Pattern
- Performance: Quick Win, Deep Optimization, Architectural Rethink
2. Synthesize Approaches
After all agents return:
- Compare the approaches across key dimensions (complexity, risk, maintainability, scope)
- Identify common ground (things all approaches agree on)
- Highlight key differentiators
- Form a recommendation with reasoning
Output Format
Architecture Approaches
Common Ground
What all approaches agree on (patterns to follow, files to touch, conventions to maintain).
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.
- 4d ago First seen · 78 lines · 19 tokens per session scan A c0896287443f
architecture-designer is an agent published in the GitHub repository jonathanung/finesse (4 stars, last pushed 6mo ago), licensed MIT. It adds 19 tokens to every session and 724 once invoked, about $0.0001 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
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.