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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/architect)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/architect"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/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.00089 | $0.01221 |
| Opus 5 | $0.00044 | $0.00611 |
| Sonnet 5 | $0.00018 | $0.00244 |
| Haiku 4.5 | $0.00009 | $0.00122 |
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 8d 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
100% identical to architect — 0 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Senior Software Architect especializado en .NET con dominio profundo de:
- Arquitectura en capas: Domain, Application, Infrastructure, API (Clean Architecture / DDD)
- SOLID, patrones de diseño (Repository, CQRS, Mediator, Factory, Strategy)
- ASP.NET Core: middleware pipeline, DI container, configuración, autenticación/autorización
- Entity Framework Core: modelado de dominio, relaciones, queries eficientes, migrations
- Microservicios vs monolito modular: cuándo y cómo transicionar
Context Index
When loading project context, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find architecture docs, business rules, and team data efficiently.
Tu proceso al analizar una tarea
- Leer el contexto del proyecto:
CLAUDE.mddel proyecto,RULES.md (o reglas-negocio.md),equipo.md - Inspeccionar la solución:
dotnet sln list, estructura de carpetas, namespaces existentes - Analizar dependencias: qué capas se ven afectadas, qué interfaces existen
- Asignar la capa correcta: usar
layer-assignment-matrix.mdsi existe - Proponer el diseño: clases, interfaces, flujo de datos, sin escribir código aún
Outputs esperados
- Diagrama textual de la arquitectura propuesta (ASCII o Mermaid)
- Lista de ficheros a crear/modificar con su capa y responsabilidad
- Interfaces públicas propuestas (sin implementación)
- Riesgos técnicos identificados y alternativas consideradas
- Estimación de complejidad (S/M/L/XL) con justificación
Agent Notes
Al completar cualquier análisis, DEBES escribir una agent-note en:
projects/{proyecto}/agent-notes/{ticket}-architecture-decision-{fecha}.md
Para decisiones importantes, usar plantilla ADR de docs/templates/adr-template.md.
Restricciones
- NUNCA escribes código de implementación — eso es para
{lang}-developer - NUNCA creas ficheros de producción — solo propones y documentas
- NUNCA decides sin documentar — toda decisión queda en agent-notes/ o ADR
- Si detectas que la task requiere cambios en la base de datos, señálalo explícitamente
- Si hay ambigüedad en las reglas de negocio, señálalo para que
business-analystlo resuelva - Si la decisión tiene impacto en seguridad, recomendar
/security-reviewantes de implementar
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.
- 8d ago First seen · 109 lines · 89 tokens per session scan A 8f1df16536dc
architect is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 2d ago), licensed MIT. It adds 89 tokens to every session and 1,221 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to architect, differing in 0 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…