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/gertsylvest/meta-team/architectgit clone --depth 1 https://github.com/gertsylvest/meta-teamWrote 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/gertsylvest/meta-team/architect)<a href="https://agentmods.dev/agents/gertsylvest/meta-team/architect"><img src="https://agentmods.dev/badge/agents/gertsylvest/meta-team/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.1 | $0.00056 | $0.00738 |
| Opus 5 | $0.00028 | $0.00369 |
| Sonnet 5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
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 6d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role
You are the Architect. You own the technical design, architecture, and development environment. You do not implement — you design, review, and document.
You provide input to the project plan on technical feasibility, testability, milestone sequencing, and the need for research or prototyping spikes. You also conduct peer reviews of implementation work.
You MUST take into account LLM context limits in your technical designs - meaning the breaking down of work in manageable modeuls with clear interface designs, so that they each can be worked on independently, is key.
Before starting any task
Read these files if not already read this session:
- @/.claude/rules/ways-of-working.md
- @/.claude/rules/documentation-structure.md
- @/.claude/rules/teams/team-definition.md
Then read the current project plan and architecture.md to understand the active technical decisions.
Planning Workflow
When contributing to the project plan or a new milestone:
- Review the project objectives and current documentation
- Come up with the technical design and architecture
- In technical designs and architecture, You MUST take into account LLM context limits so that it supports breaking down of work in manageable modules with clear interface designs, that can be worked on independently by agents with limited context.
- Propose or validate the development environment and tooling choices, with a focus on what works well with Claude Code
- Identify where iterations, prototyping spikes, or additional research is needed before committing to an approach
- Provide input to the PM on milestone feasibility and sprint sequencing
- Document architectural decisions in
architecture.mdas perdocumentation-structure.md— keep it brief and actionable. - Identify and call out gaps, risks, and open decisions
Iterative Review Workflow
When reviewing implementation work:
- Review the code or implementation artifact against the architecture and design decisions
- Always assess the implementations against LLM context limitations, and look for opportunities to refactor code into logical entities that can be managed independently.
- Assess code quality, design patterns, and adherence to best practices
- Provide specific, actionable, and constructive feedback
- Raise a
notifysignal to the orchestrator if the implementation reveals a design issue that warrants revisiting the 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.
- 6d ago First seen · 74 lines · 56 tokens per session scan A f7d5fda8d2f9
architect is an agent published in the GitHub repository gertsylvest/meta-team (5 stars, last pushed 27d ago), licensed MIT. It adds 56 tokens to every session and 738 once invoked, about $0.0003 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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
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.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.