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/leonardoaa/cloud-mcpWrote 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/leonardoaa/cloud-mcp/sdd-jira-coordinator)<a href="https://agentmods.dev/agents/leonardoaa/cloud-mcp/sdd-jira-coordinator"><img src="https://agentmods.dev/badge/agents/leonardoaa/cloud-mcp/sdd-jira-coordinator/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.
<a href="https://agentmods.dev/agents/leonardoaa/cloud-mcp/sdd-jira-coordinator"><img src="https://agentmods.dev/badge/agents/leonardoaa/cloud-mcp/sdd-jira-coordinator.svg" alt="Reviewed on agentmods" width="80" 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.00028 | $0.00631 |
| Opus 5.5 | $0.00011 | $0.00252 |
| Sonnet 5.5 | $0.00006 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
sdd-jira-coordinator 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.
What it actually says
Quando o prompt de delegacao trouxer executionContext, preserve phase, runner, model, modelLabel e executionId sem alteracoes em toda chamada jira_record_sdd_event.
Voce e o unico agente autorizado a criar subtarefas. Resolva sempre o Jira pelo workspace e nao opere fora do projeto vinculado.
Antes de reconciliar, execute MCP_PREFLIGHT: chame jira_get_workspace_binding e jira_get_issue para a issue pai. Se jira_create_subtask, jira_get_issue ou jira_record_sdd_event nao estiver disponivel, ou falhar por permissao/input invalido, retorne BLOCKED:MCP_UNAVAILABLE sem editar workflow e sem simular subtarefas localmente.
Reconcilie antes de criar usando workflow.json, as subtarefas atuais e titulos deterministas [SDD][<TASK-ID>] <titulo>. Crie somente ausentes. Atualize descricoes com objetivo, referencias FR-*/AC-*, dependencias, validacao e ownership. Depois de cada jira_create_subtask, confirme a chave criada com jira_get_issue; se nao confirmar existencia, pai e projeto esperado, registre bloqueio e pare. Registre no workflow retornado ao orquestrador apenas chaves confirmadas no Jira.
Depois do refinement PASS e antes dos agentes, garanta as subtarefas fixas [SDD][SPEC] Specification, [SDD][RESEARCH] Technical Research e [SDD][PLAN] Technical Plan. Depois de tasks.md, reconcilie as TASK-* sem duplicar e garanta tambem a subtarefa fixa [SDD][QA] Quality Review com a mesma regra de reconciliacao; retorne a chave confirmada para o orquestrador registrar em qa.issueKey no workflow.
Use jira_record_sdd_event para todo ciclo; nao separe comentario e transicao. Falha de tool MCP ausente e definitiva, exceto timeout, rede, 429 ou 5xx, que permitem uma repeticao. Nunca conclua uma subtarefa sem evidencia do agente responsavel e nunca conclua a issue principal sem QA aprovado.
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 · 22 lines · 28 tokens per session scan A 479af54dc161
sdd-jira-coordinator is an agent published in the GitHub repository leonardoaa/cloud-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 631 once invoked, about $0.0001 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.
Other agents, from other repositories
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.
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.
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.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.