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/developmentagentsdd/mcp-jiracloud/analysisgit clone --depth 1 https://github.com/DevelopmentAgentSDD/MCP-JiraCloudWhat 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 | $0.00042 | $0.00711 |
| Opus 5 | $0.00021 | $0.00356 |
| Sonnet 5 | $0.00008 | $0.00142 |
| Haiku 4.5 | $0.00004 | $0.00071 |
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 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.
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 contextsbusiness-rules.md— Reglas de negocio catalogadasevent-storming.md— Timeline de eventos de dominioapi-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
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.
- yesterday First seen · 79 lines · 42 tokens per session scan A 50792249b7fc
analysis is an agent published in the GitHub repository DevelopmentAgentSDD/MCP-JiraCloud (0 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 711 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.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
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.
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.
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.