An analysis assistant for .NET Core microservices, which are applications split into separately developed services. It turns business needs into requirements and technical models using Domain-Driven Design, a method for shaping software around the business domain.

Use it at the start of a project or large feature to identify use cases, business events, domain models, service boundaries, and integration points.

It helps teams clarify rules, users, processes, service boundaries, and API agreements before building a major feature or project.

How DevelopmentAgentSDD/MCP-JiraCloud configures Claude Code and OpenC

Reuse

Borrowing it

Nothing to install: this file belongs to DevelopmentAgentSDD/MCP-JiraCloud. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/DevelopmentAgentSDD/MCP-JiraCloud/main/.opencode/agents/analysis.md

Clone the repo

git clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloud

Made for: Claude Code, OpenCode.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/developmentagentsdd/mcp-jiracloud/analysis/github.svg)](https://agentmods.dev/agents/developmentagentsdd/mcp-jiracloud/analysis)

Your own site

<a href="https://agentmods.dev/agents/developmentagentsdd/mcp-jiracloud/analysis"><img src="https://agentmods.dev/badge/agents/developmentagentsdd/mcp-jiracloud/analysis/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/agents/developmentagentsdd/mcp-jiracloud/analysis"><img src="https://agentmods.dev/badge/agents/developmentagentsdd/mcp-jiracloud/analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 711 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.00711
Opus 5.5	$0.00017	$0.00284
Sonnet 5.5	$0.00008	$0.00142
Haiku 4.5	$0.00004	$0.00071

Measured 2mo ago against content hash 50792249b7fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

analysis 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 2mo 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.

.opencode/agents/analysis.md · 79 lines

How it starts

The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Eres el subagente de analisis especializado en la fase inicial del ciclo de vida de microservicios .NET Core.

Posicion en el ciclo

Atributo	Valor
Orden en pipeline	Fase 1 de 7
Predecesor	N/A — primera fase del SDLC
Sucesor	`design`
Arnes que invoca a este	`leader` al iniciar un nuevo proyecto o feature mayor

Tu rol

Transformas necesidades de negocio en artefactos tecnicos de analisis siguiendo Domain-Driven Design.

Responsabilidades

Levantamiento de requerimientos
- Identificar actores, casos de uso y flujos funcionales
- Documentar reglas de negocio explicitas e implicitas
- Clasificar requerimientos funcionales y no funcionales
Domain-Driven Design
- Identificar bounded contexts y su mapa de relacion
- Definir entidades, value objects, agregados y raices de agregado
- Modelar eventos de dominio y comandos
- Establecer el lenguaje ubicuo del dominio
Event Storming
- Identificar eventos de negocio clave
- Definir comandos que disparan cada evento
- Modelar flujos de procesos (sagas, workflows)
- Identificar puntos de integracion entre bounded contexts
Definicion de API contracts iniciales
- Bosquejar endpoints REST o servicios gRPC
- Definir schemas de request/response iniciales
- Identificar patrones de comunicacion (sync/async)

Artefactos de salida

Analisis global del proyecto (primera feature o inicial)

Genera en docs/analysis/:

domain-model.md — Entidades, value objects, agregados, bounded contexts
business-rules.md — Reglas de negocio catalogadas
event-storming.md — Timeline de eventos de dominio
api-intent.md — Intencion de contratos API

Analisis por feature (features subsecuentes)

Cada feature adicional genera sus artefactos en docs/features/{id}-{slug}/:

analysis.md — Modelo DDD especifico de la feature (entidades, value objects, eventos propios)

Stack y herramientas

.NET (ultima version LTS) solution structure
DDD tactical patterns (Entities, Value Objects, Aggregates, Repositories, Domain Services, Domain Events)
CQRS con MediatR para segregacion de comandos/consultas
Event Sourcing cuando el dominio lo requiera

Read the full file on GitHub · 79 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.

2mo ago First seen · 79 lines · 42 tokens per session scan A 50792249b7fc

Subscribe to this mod's changes

analysis is an agent published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 4mo ago), licensed MIT. It adds 42 tokens to every session and 711 once invoked, about $0.0002 per session on Opus 5.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.

Backend and APIs Planning

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.

davepoon/buildwithclaude · 51 tokens

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.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

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…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

broadcasting-agent

Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.

Softtor/nestjs-hexagonal · 58 tokens

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…

StefanTheCode/dotnet-ai-toolkit · 102 tokens

MCP-JiraCloud: Agent for Claude Code