sync-confluence

A guide for publishing engineering Markdown documents from docs/engineering/ to Confluence Cloud, an online platform for shared team documentation. It supports local setup and automated syncing for marked documents.

In plain words
What is it for?
Use it to scaffold engineering documentation folders or configure a CI process that publishes ADRs, RFCs, and architecture documents to Confluence.
Why use it?
It provides a defined path from repository documentation to the team’s Confluence pages and limits syncing to documents with the required metadata.

Skill for Claude CodeCodex

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 skills/soulcodex/agentic/sync-confluence
Any agent
npx skills add soulcodex/agentic --skill sync-confluence
Clone the repo
git clone --depth 1 https://github.com/soulcodex/agentic

Made for: Claude Code, Codex.

Per session 81 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. 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.00081 $0.01149
Opus 5 $0.00041 $0.00575
Sonnet 5 $0.00016 $0.00230
Haiku 4.5 $0.00008 $0.00115

Measured 2d ago against content hash df36eaa86d73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

sync-confluence scanned grade B with 1 finding 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 2d 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

### Step A4 — Output instructions
skills/documentation/sync-confluence/SKILL.md · 181 lines

How it starts

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

Sync Confluence Skill

This skill syncs Markdown documentation from docs/engineering/ to Confluence Cloud using the mark tool. It operates in two distinct modes.


Mode A — Scaffold (run once, locally)

Triggered when docs/engineering/ does not exist. Run this once before any CI sync.

Step A1 — Verify prerequisites

Ensure mark is installed:

mark --version

If not installed: brew install mark or go install github.com/kovetskiy/mark@latest.

Step A2 — Create directory structure

Creates the full tree with INDEX.md stubs:

docs/engineering/
├── INDEX.md
├── adr/
│   └── INDEX.md
├── rfc/
│   └── INDEX.md
└── architecture/
    ├── INDEX.md
    └── resources/

Step A3 — Add sample documents

Creates one example ADR and one example RFC using the templates so engineers have a concrete reference to copy from.

Step A4 — Output instructions

After scaffolding, output:

Scaffold complete. Next steps:

  1. Review and commit the new directory structure
  2. Add mark metadata headers to your documents
  3. Configure CONFLUENCE_* secrets in your CI environment
  4. Push to main — CI sync will run automatically

Do NOT push to Confluence in scaffold mode.


Mode B — CI Sync (run on every push to main)

Triggered in CI. No interactive prompts. Fails fast on any error.

Step B1 — Verify environment

Check required env vars are set:

: "${CONFLUENCE_URL:?missing}"
: "${CONFLUENCE_USER:?missing}"
: "${CONFLUENCE_API_TOKEN:?missing}"

Exit 1 if any are missing.

Step B2 — Verify scaffold exists

test -d docs/engineering || exit 1

Exit 1 if docs/engineering/ does not exist (scaffold was not run).

Step B3 — Scan for eligible documents

Scan for files with mark headers:

find docs/engineering/adr docs/engineering/rfc docs/engineering/architecture \
  -name '*.md' -exec grep -l '<!-- Space:' {} \;

Step B4 — Diagram enforcement

Mermaid: Supported natively by mark. No action needed.

Read the full file on GitHub · 181 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 2d ago First seen · 181 lines · 81 tokens per session scan B df36eaa86d73

Subscribe to this mod's changes

sync-confluence is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 2d ago), licensed MIT. It adds 81 tokens to every session and 1,149 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

help

Use when asked what the capstone plugin can do - prints the usage block.

GentBajko/capstone · 18 tokens

core

Internal to the capstone suite - carries the shared rules (references/) and scripts every capstone subcommand reads; it exists so npx-skills installs ship them alongside the command skills. Not meant to be invoked directly; when invoked anyway, run references/../scripts/help.sh and output its stdout verbatim.

GentBajko/capstone · 65 tokens

groom

Use when starting work on a feature or change for a project that already has capstone docs - "new feature", "add a feature", "implement X", "build X", "design a feature", "spec it out", "flesh out", "refine this idea", "let's work on X" - a doc-grounded one-question-at-a-time interview producing a traceable feature…

GentBajko/capstone · 135 tokens

map

Use when asked to build, refresh, update, or check a codebase's architecture reference docs - "map the codebase", "document this repo", "are the docs current", "bring the docs in line with the code" - writes a docs/capstone/ index plus topic chapters, the logic/ business-logic map and the uiux/ surface map, then on…

GentBajko/capstone · 141 tokens

feature

Use when the user wants one feature taken from idea to working code - "add a feature", "build X end to end", "take X from idea to shipped" - runs the feature chain groom -> plan -> implement consecutively, detecting the feature's stage and resuming at the first incomplete one. For the whole-product greenfield pipeline…

GentBajko/capstone · 82 tokens

review

Use when asked for an opinionated review of the codebase - architecture/backend findings, UI findings against the project's own design docs, or both - severity-ranked with evidence, written to docs/capstone/review.md. Bare "review" does both sides; "review backend" or "review frontend" does one. Opt-in judgment; never…

GentBajko/capstone · 74 tokens