A command for documenting one or more projects in Confluence, a team website for shared documentation. It can create or update the relevant pages on the connected Confluence site.

Use it to create project documentation or update documentation pages for one or more projects.

It avoids manually copying project information into team documentation and helps keep existing pages current.

sdd-doc — Command for Claude Code by leonardoaa/cloud-mcp

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.

Clone the repo

git clone --depth 1 https://github.com/leonardoaa/cloud-mcp

Made for: Claude Code.

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/commands/leonardoaa/cloud-mcp/sdd-doc/github.svg)](https://agentmods.dev/commands/leonardoaa/cloud-mcp/sdd-doc)

Your own site

<a href="https://agentmods.dev/commands/leonardoaa/cloud-mcp/sdd-doc"><img src="https://agentmods.dev/badge/commands/leonardoaa/cloud-mcp/sdd-doc/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/commands/leonardoaa/cloud-mcp/sdd-doc"><img src="https://agentmods.dev/badge/commands/leonardoaa/cloud-mcp/sdd-doc.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 992 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.00020	$0.00992
Opus 5.5	$0.00008	$0.00397
Sonnet 5.5	$0.00004	$0.00198
Haiku 4.5	$0.00002	$0.00099

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

Security

Grade A, and why

sdd-doc 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.

resources/sdd/commands/sdd-doc.md · 32 lines

What it actually says

Voce esta executando /sdd-doc para documentar projetos no Confluence. Entrada: $ARGUMENTS.

Este comando e desacoplado de /sdd-task, /sdd-plan e /sdd-build: nao cria issues, subtarefas, specs, branches nem registra eventos SDD. Ele apenas le o repositorio e grava documentacao no Confluence do mesmo site Atlassian do perfil vinculado.

Regras obrigatorias:

Execute o JIRA_GATE: identifique o workspacePath e chame jira_get_workspace_binding. O binding resolve o perfil e, portanto, o site Confluence (${baseUrl}/wiki). Sem vinculo, liste perfis com jira_list_profiles, pergunte qual perfil usar, vincule com jira_bind_workspace e valide de novo. Sem contexto valido, encerre.
Execute o MULTI_GATE do bloco multi-projeto para descobrir quais workspaces vinculados participam. Com 2+ vinculados, confirme com o usuario a lista final de projetos e a ordem. Com 1, siga em modo single.
Confirme com o usuario o nome do produto (titulo da pagina-HUB) e o space Confluence de destino. Chame confluence_list_spaces para listar as opcoes; aceite tambem uma chave informada diretamente (spaces pessoais tem chave ~<accountId>).
AVISO DE SEGREDOS: esta doc grava senhas e chaves em texto claro. Antes de escrever, confirme explicitamente com o usuario que o space escolhido e restrito. Se ele recusar ou o space for aberto, nao grave a secao de segredos.
Interprete pela frase do usuario se a intencao e criar ou atualizar, mas SEMPRE valide contra o Confluence antes de gravar: chame confluence_find_page(spaceKey, title) para o HUB e para cada pagina filha. Pagina existente -> atualizar (preservando o que ainda vale e atualizando as secoes); ausente -> criar. Nunca crie cega quando ja existe pagina de mesmo titulo no space.
Trate o HUB primeiro: localize ou crie a pagina-HUB e capture seu pageId, pois ele e o parentId das filhas. Monte o HUB conforme o padrao (secao "Pagina-HUB").
Para cada projeto, na ordem definida, delegue exatamente subagent_type: "sdd-doc-writer", passando: workspacePath do projeto, spaceKey, parentId (o pageId do HUB), o titulo da pagina filha, a decisao criar/atualizar ja validada e se a secao de segredos foi autorizada. Nunca use code, developer ou agente generico. Nao use run_in_background.
Depois que todas as filhas existirem, atualize no HUB a tabela "Projetos do produto", a secao "Ambientes" consolidada e o "Indice" com os links das filhas (use confluence_update_page no HUB).
Ao final, liste por pagina: titulo, acao (criada/atualizada), URL e projeto correspondente. Relate qualquer projeto pulado e o motivo.

Protocolo de erro: em falha transitoria (timeout, rede, 429, 5xx) repita uma vez a mesma chamada. Em falha definitiva (tool MCP ausente, permissao, input invalido, space nao encontrado), pare e reporte sem gravar paginas parciais. Nunca invente conteudo como fallback.

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 · 32 lines · 20 tokens per session scan A 3bf133d0149a

Subscribe to this mod's changes

sdd-doc is a command published in the GitHub repository leonardoaa/cloud-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 992 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.

Writing and docs

sdd-doc

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

converge

implement

speckit.bug.fix