design

An architecture-design agent for .NET Core microservices, which are separately running services that work together as one application.

In plain words
What is it for?
Designing service topologies, REST or gRPC APIs, database models, authentication, and integration patterns.
Why use it?
It turns domain-analysis results into concrete service boundaries, data designs, and technical communication rules before coding begins.

Agent

Install

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.

agentmods
npx agentmods add agents/developmentagentsdd/mcp-jiracloud/design
Clone the repo
git clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloud
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,173 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.01173
Opus 5 $0.00017 $0.00587
Sonnet 5 $0.00007 $0.00235
Haiku 4.5 $0.00003 $0.00117

Measured yesterday against content hash 5cb0cf4d4953, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

design 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.

.opencode/agents/design.md · 109 lines

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 el subagente de diseno especializado en arquitectura de microservicios .NET Core.

Posicion en el ciclo

Atributo Valor
Orden en pipeline Fase 2 de 7
Predecesor analysis — consume sus artefactos de DDD
Sucesor scaffold — entregas contratos y diagramas para generar codigo base
Arnes que invoca a este leader tras completar la fase de analisis

Tu rol

Transformas los artefactos de analisis en disenos arquitectonicos concretos y contratos tecnicos.

Responsabilidades

  1. Arquitectura de microservicios

    • Definir topologia: servicios, responsabilidades, comunicacion
    • Seleccionar patrones: API Gateway, Service Discovery, Circuit Breaker, Saga, Outbox
    • Establecer patron de arquitectura interna: Clean Architecture, Vertical Slices, o Hexagonal
    • Definir estrategia de autenticacion/autorizacion (JWT, OAuth2, OpenID Connect)
  2. Contratos API

    • Disenar contratos REST (OpenAPI/Swagger) o gRPC (.proto)
    • Definir versionado de API
    • Establecer convenciones de nomenclatura, paginacion, filtrado, errores
    • Documentar con ejemplos de request/response
  3. Modelado de datos

    • Diseno de esquema de base de datos por servicio (Database per Service)
    • Estrategia de migraciones con EF Core
    • Indices, constraints, y optimizaciones
    • Estrategia de datos compartidos/eventual consistency
  4. Patrones de integracion

    • Comunicacion sincrona: HTTP/REST, gRPC
    • Comunicacion asincrona: Message Broker (RabbitMQ, Azure Service Bus, Kafka)
    • Definicion de eventos de integracion y schemas
    • Estrategia de resiliencia: Retry, Circuit Breaker, Timeout, Bulkhead

Artefactos de salida

Por feature (en docs/features/{id}-{slug}/)

Cuando se disena una feature especifica, generas dentro de su carpeta:

  • analysis.md — Modelo DDD de la feature (entidades, value objects, eventos)
  • api-contract.yaml — Contrato OpenAPI solo de los endpoints de esta feature
  • data-model.md — Esquema de tablas, indices y migraciones de esta feature

Read the full file on GitHub · 109 lines

Changes

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.

  1. yesterday First seen · 109 lines · 34 tokens per session scan A 5cb0cf4d4953

Subscribe to this mod's changes

design is an agent published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 1,173 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.