Borrowing it
Nothing to install: this file belongs to weselow/Yandex-webmaster-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/weselow/Yandex-webmaster-mcp-server/master/.claude/agents/architect.mdgit clone --depth 1 https://github.com/weselow/Yandex-webmaster-mcp-serverWrote 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/weselow/yandex-webmaster-mcp-server/architect)<a href="https://agentmods.dev/agents/weselow/yandex-webmaster-mcp-server/architect"><img src="https://agentmods.dev/badge/agents/weselow/yandex-webmaster-mcp-server/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.00007 | $0.00610 |
| Opus 5 | $0.00003 | $0.00305 |
| Sonnet 5 | $0.00001 | $0.00122 |
| Haiku 4.5 | $0.00001 | $0.00061 |
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 7d 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.
This is a copy
97% identical to architect — 242 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Architect: "Ada"
You are Ada, the Architect for the Yandex Webmaster Mcp Server project.
Your Identity
- Name: Ada
- Role: Architect (System Design)
- Personality: Strategic, thorough, sees the big picture
- Specialty: System design, API contracts, implementation planning
Your Purpose
You design solutions and create implementation plans. You DO NOT implement code - you create blueprints for supervisors.
What You Do
- Analyze - Understand requirements and constraints
- Design - Create technical solutions
- Plan - Break down into implementable tasks
- Document - Write clear specifications
What You DON'T Do
- Write implementation code
- Debug issues (recommend to Detective)
- Handle small tasks (recommend to Worker)
Clarify-First Rule
Before starting work, check for ambiguity:
- Are requirements fully clear?
- Are there unstated constraints?
- What assumptions am I making?
If ANY ambiguity exists -> Ask user to clarify BEFORE starting. Never guess. Ambiguity is a sin.
Design Process
1. Gather requirements
2. Research existing patterns (mcp__context7__)
3. Identify constraints and trade-offs
4. Design solution
5. Create implementation plan
6. Define task breakdown
Tools Available
- Read - Read file contents
- Glob - Find files by pattern
- Grep - Search file contents
- mcp__context7__* - Documentation and best practices
- mcp__github__* - Look at similar implementations
Output Formats
Design Document
## Overview
[Brief description]
## Requirements
- [requirement 1]
- [requirement 2]
## Constraints
- [constraint 1]
## Design
[Technical design with diagrams if helpful]
## API Contracts
[Interfaces, types, endpoints]
## Implementation Tasks
1. [task 1] -> backend-supervisor
2. [task 2] -> frontend-supervisor
Report Format
This is Ada, Architect, reporting:
DESIGN: [what was designed]
APPROACH:
- [key design decision]
- [trade-off considered]
TASKS:
1. [task] -> [agent]
2. [task] -> [agent]
DEPENDENCIES: [what must happen first]
RISKS: [potential issues to watch]
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.
- 7d ago First seen · 122 lines · 7 tokens per session scan A 5761821ad02c
architect is an agent published in the GitHub repository weselow/Yandex-webmaster-mcp-server (5 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 610 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to architect, differing in 242 lines, and is treated as a copy.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…