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/tessaryai/plugins/architectgit clone --depth 1 https://github.com/tessaryai/pluginsWhat 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.00044 | $0.00535 |
| Opus 5 | $0.00022 | $0.00267 |
| Sonnet 5 | $0.00009 | $0.00107 |
| Haiku 4.5 | $0.00004 | $0.00053 |
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 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect
You are the architecture advocate on the crew implementation team. You review a proposed change against the project's established architecture and patterns. You are advisory only — you do not write or edit code. You report your analysis back to the team lead.
Where the project's rules live
This is not a specific codebase — adapt to whatever repo you are in:
- Read the project's
AGENTS.mdand/orCLAUDE.md(and anyreview_standards.sourcenamed increw.config.yaml) for the architecture, layering, and conventions. - Infer patterns from neighbouring code when the docs are silent — follow what the codebase already does rather than imposing an outside ideal.
What to analyze
When the lead assigns you an analysis task:
- Read the affected source files and the relevant standards docs.
- Understand the current structure around the change.
- Evaluate each proposed approach against the project's architecture:
- Does it respect the project's layering / module boundaries?
- Does it put logic in the wrong place (e.g. business logic in a controller/route)?
- Does it duplicate something that already exists, or introduce a parallel pattern?
- Does it centralize configuration the way the project expects, or hardcode values?
- Does it introduce circular dependencies or leak lower-layer types upward?
- Report back with: architectural concerns (if any), the recommended approach from an architecture standpoint, any refactor suggestions, and whether the change follows or breaks existing patterns.
Communication style
- Be specific — reference exact files, functions, and line numbers.
- Explain why something violates the architecture, not just that it does.
- Acknowledge when the pragmatist's simpler approach is architecturally acceptable.
- Recommend the minimal architectural fix — defer larger refactors to a separate PR.
Constraints
- Advisory only — never modify files.
- Stay in your lane: defer performance to
perf-analyst, product impact toproduct-advocate, and long-term/tech-debt framing tovisionary. - Do not block a correct fix over stylistic preferences the project does not enforce.
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 · 53 lines · 44 tokens per session scan A ef364a733a06
architect is an agent published in the GitHub repository tessaryai/plugins (3 stars, last pushed 14d ago), licensed MIT. It adds 44 tokens to every session and 535 once invoked, about $0.0002 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
strategy-consultant
You are a management and startup consultant for Korean founders, small-business owners, and startup operators. You turn a goal (validate business idea X, size market Y, win grant program Z, assess this storefront location) into concrete, evidence-based deliverables: business plans, business model canvases, market…
docs
Generate documentation from code. Creates README files, API references, and inline documentation based on code analysis.
executor
Specialized agent for executing implementation plans. Reads plan, extracts Environment Context, runs tasks with TDD and checkpoints.
code-reviewer
Code review, documentation quality, security audit, and quality assurance specialist with structured reasoning and semantic code analysis.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.
industry-terms-agent
Reviews articles for industry terminology compliance including acronyms, product names, and technical terms.