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 instructions/hamza-xp/confluence-mcp-server/claude-mdgit clone --depth 1 https://github.com/Hamza-XP/confluence-mcp-serverWrote 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/instructions/hamza-xp/confluence-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/hamza-xp/confluence-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/hamza-xp/confluence-mcp-server/claude-md.svg" alt="Measured on agentmods" 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.01155 | $0.01155 |
| Opus 5 | $0.00577 | $0.00577 |
| Sonnet 5 | $0.00231 | $0.00231 |
| Haiku 4.5 | $0.00115 | $0.00115 |
Grade A, and why
confluence-mcp-server CLAUDE.md 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Guidance for Claude (or any agent) using this MCP server's tools to work with Confluence. Read this before creating or editing any page — it defines the house style so that content from different people and different sessions stays consistent.
Before creating anything: explore first, never guess
- Call
list_spacesto get real space keys. Display names in the UI often differ from the key (e.g. a space titled "Portali" may have keyPortali1). - Call
list_childrenon the space's home page, then recurse into any folders it returns, to build the actual structure before deciding where new content goes. Confluence Cloud has a native "Folder" content type distinct from pages — always letlist_childrenshow you both (this server's implementation already queries/child/pageand/child/folderand merges them; if you're extending this server, preserve that). - Call
search_pagesfor the topic you're about to document. If a page already covers it, update it or skip it — do not create a duplicate. Only write new pages for material that genuinely isn't there yet. - Match the existing convention in that space/folder (flat numbered pages vs. nested folders, emoji-prefixed titles vs. plain, etc.) rather than imposing your own structure.
Standard document structure
When compiling infrastructure or task documentation (as opposed to editing something freeform), use this section order. Omit a section entirely if you have no real source material for it — never fabricate content to fill a template:
- Overview — one paragraph: what this system/project is
- Repositories — links and relevant branches, if applicable
- AWS Account & Region (or equivalent cloud provider info) — a table: component, region, notes
- Architecture — key components and how they connect
- Environment Variables / Configuration — what's documented; see the credentials note below before including actual values
- Deployment Runbook — concrete, step-by-step, copy-pasteable commands
- CI/CD Pipeline — if documented
- Supporting Infrastructure — anything that doesn't fit above (CDN, WAF, monitoring, etc.)
- Known Issues / Troubleshooting
- Open Questions / Gaps — things referenced but unexplained, or where sources conflict
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.
- 5d ago First seen · 91 lines · 1,155 tokens per session scan A 4278f11c3018
confluence-mcp-server CLAUDE.md is an instructions file published in the GitHub repository Hamza-XP/confluence-mcp-server (3 stars, last pushed 26d ago), licensed MIT. It adds 1,155 tokens to every session, about $0.0058 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.