What is mcp-atlassian-dc AGENTS.md?

Project instructions for MCP Atlassian, a Python server that connects coding agents to Jira and Confluence through the Model Context Protocol. They describe the source layout, clients, tools, configuration, and tests.

They are for developing, testing, linting, configuring, and running the Jira and Confluence integrations.

They provide the development rules and architecture needed to work safely in the repository. This helps an agent find the right code and run the required checks.

How tuongbeo/mcp-atlassian-dc configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to tuongbeo/mcp-atlassian-dc. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/tuongbeo/mcp-atlassian-dc/cloudflare-worker-multi/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/tuongbeo/mcp-atlassian-dc

Made for: Codex, OpenCode.

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/instructions/tuongbeo/mcp-atlassian-dc/agents-md/github.svg)](https://agentmods.dev/instructions/tuongbeo/mcp-atlassian-dc/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/tuongbeo/mcp-atlassian-dc/agents-md"><img src="https://agentmods.dev/badge/instructions/tuongbeo/mcp-atlassian-dc/agents-md/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/instructions/tuongbeo/mcp-atlassian-dc/agents-md"><img src="https://agentmods.dev/badge/instructions/tuongbeo/mcp-atlassian-dc/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,055 This file is loaded in full into every session.

When invoked 1,055 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin 91% copy Near-identical to another mod 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.01055	$0.01055
Opus 5	$0.00528	$0.00528
Sonnet 5	$0.00211	$0.00211
Haiku 4.5	$0.00105	$0.00105

Measured 7d ago against content hash 0a5dc39ba54d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

mcp-atlassian-dc AGENTS.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 7d 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.

Origin

This is a copy

91% identical to mcp-atlassian AGENTS.md — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 97 lines

How it starts

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

MCP Atlassian

Audience: LLM-driven engineering agents

Repository map

Path	Purpose
`src/mcp_atlassian/`	Library source (Python ≥ 3.10)
`├─ jira/`	Jira client + 16 mixins (issues, search, SLA, metrics, …)
`├─ confluence/`	Confluence client + 7 mixins (pages, search, analytics, …)
`├─ models/`	Pydantic v2 data models (`ApiModel` base)
`├─ servers/`	FastMCP server instances (`jira_mcp`, `confluence_mcp`)
`├─ preprocessing/`	Content conversion (ADF/Storage → Markdown)
`└─ utils/`	Shared utilities (auth, logging, SSL, decorators)
`tests/`	Pytest suite — unit, integration, real-API validation
`scripts/`	OAuth setup and testing scripts

Architecture

Mixin composition: JiraFetcher composes 16 mixins, ConfluenceFetcher composes 7. Client inheritance is transitive through mixins.
FastMCP servers: servers/main.py → lifespan → dependency injection via get_jira_fetcher(ctx) / get_confluence_fetcher(ctx).
Tool naming: {service}_{action}_{target} (e.g., jira_create_issue, confluence_get_page).
Config: Environment-based from_env() factory on JiraConfig / ConfluenceConfig dataclasses.
Auth: Basic (Cloud + Server/DC), PAT (Server/DC), OAuth 2.0 (Cloud + Server/DC) — with multi-tenant header support.
Models: All extend ApiModel → from_api_response() + to_simplified_dict().

Dev workflow

uv sync --frozen --all-extras --dev  # install dependencies
pre-commit install                    # setup hooks
pre-commit run --all-files           # Ruff + mypy
uv run pytest -xvs                   # full test suite
uv run pytest tests/unit/ -xvs       # unit tests only
uv run pytest tests/integration/     # integration tests
uv run pytest --cov=src/mcp_atlassian --cov-report=term-missing  # coverage

Tests must pass and lint/typing must be clean before committing.

Rules

Package management: ONLY use uv, NEVER pip
Branching: NEVER work on main, always create feature branches
Type safety: All functions require type hints
Testing: New features need tests, bug fixes need regression tests
Commits: Use trailers for attribution, never mention tools/AI
Commit types: feat, fix, docs, refactor, test, chore, perf, ci — scopes: jira, confluence, server, auth, docker, docs
File hygiene: Prefer editing existing files over creating new ones

Read the full file on GitHub · 97 lines

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.

7d ago First seen · 97 lines · 1,055 tokens per session scan A 0a5dc39ba54d

Subscribe to this mod's changes

mcp-atlassian-dc AGENTS.md is an instructions file published in the GitHub repository tuongbeo/mcp-atlassian-dc (0 stars, last pushed 3mo ago), licensed MIT. It adds 1,055 tokens to every session, about $0.0053 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to mcp-atlassian AGENTS.md, differing in 7 lines, and is treated as a copy.

Project management

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

mcp-atlassian-dc: Instructions file for Codex