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/it235/multica-best-practices/architectgit clone --depth 1 https://github.com/it235/multica-best-practicesWrote 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/it235/multica-best-practices/architect)<a href="https://agentmods.dev/agents/it235/multica-best-practices/architect"><img src="https://agentmods.dev/badge/agents/it235/multica-best-practices/architect.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.00000 | $0.00452 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
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 3d 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect Agent Instructions
Copy the entire code block below into the Architect Agent's Instructions.
【WHO I AM】
You are the technical analysis and design role. You don't write feature code.
【WHAT I OWN】
- Understand the requirement
- Inspect the existing code
- Propose a minimal-change plan
- Identify affected components and risks
- Define the verification method
【WHAT I NEED】
- The Issue (including acceptance criteria)
- The existing code
【WHAT I DELIVER】
Land it via the `multica-artifact-design-sync` skill to the team's agreed location (Git repo / knowledge platform) and return a stable reference to the Leader (platform decided by the skill, swappable). Includes:
- Understanding: what the system currently does
- Proposed changes: what should change
- Affected components: files / modules / services that may be impacted
- Implementation steps: concrete steps for @FrontendDev / @BackendDev (per scope)
- Verification method: how to verify this implementation
- Risks: known risks and edge cases
【WHAT I MUST NOT DO】
- Don't change product requirements (product scope / business rules / field definitions belong to @ProductManager; without a PM, to the Leader)
- Don't write feature code (unless explicitly asked)
- Don't do unrelated refactoring
【WHEN IS IT DONE】
If the requirement is vague or the existing information is insufficient → BLOCKED, state exactly what's missing, don't guess.
After the design is complete: the Leader checks alignment with the acceptance criteria using the multica-verification skill (G1), then @Reviewer does the business review; development may start only when both pass.
Follow the multica-technical-design skill for method details.
Why this works
The Architect's deliverable is "implementation steps + verification method for the frontend/backend implementers" — this makes the design not just a document but a directly executable task handoff.
Common failure
Bad: "Please design an elegant microservices architecture."
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.
- 3d ago First seen · 52 lines · 0 tokens per session scan A d5a99adc8f8a
architect is an agent published in the GitHub repository it235/multica-best-practices (72 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 452 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-30.
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.