mcp-atlassian AGENTS.md

mcp-atlassian AGENTS.md is an instructions file for Codex, OpenCode from voarsh2/mcp-atlassian. It costs 1,055 tokens per session, scanned A, a copy of mcp-atlassian AGENTS.md, MIT.

Repository instructions for an AI coding agent working on mcp-atlassian, a Python server that connects to Jira and Confluence. They describe the code layout, architecture, development process, and project rules.

In plain words
What is it for?
Use them when developing, testing, or reviewing the mcp-atlassian codebase, especially its Jira and Confluence integrations.
Why use it?
They give the agent the project context and working rules it needs to make changes in the right places and follow the repository’s expected workflow.

Instructions file for CodexOpenCode

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 instructions/voarsh2/mcp-atlassian/agents-md
Clone the repo
git clone --depth 1 https://github.com/voarsh2/mcp-atlassian

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.

agentmods badge for mcp-atlassian AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/voarsh2/mcp-atlassian/agents-md.svg)](https://agentmods.dev/instructions/voarsh2/mcp-atlassian/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/voarsh2/mcp-atlassian/agents-md"><img src="https://agentmods.dev/badge/instructions/voarsh2/mcp-atlassian/agents-md.svg" alt="Measured on agentmods" 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. Scan, not verified.
Origin 94% 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.

ModelPer sessionOnce invoked
Fable 5 $0.01055 $0.01055
Opus 5 $0.00528 $0.00528
Sonnet 5 $0.00211 $0.00211
Haiku 4.5 $0.00105 $0.00105

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

Security

Grade A, and why

mcp-atlassian 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 3d 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

94% identical to mcp-atlassian AGENTS.md — 1 line 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 + 21 mixins (issues, search, SLA, metrics, …)
├─ confluence/ Confluence client + 8 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 21 mixins, ConfluenceFetcher composes 8. 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 ApiModelfrom_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

  1. Package management: ONLY use uv, NEVER pip
  2. Branching: NEVER work on main, always create feature branches
  3. Type safety: All functions require type hints
  4. Testing: New features need tests, bug fixes need regression tests
  5. Commits: Use trailers for attribution, never mention tools/AI
  6. Commit types: feat, fix, docs, refactor, test, chore, perf, ci — scopes: jira, confluence, server, auth, docker, docs
  7. 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.

  1. 3d ago First seen · 97 lines · 1,055 tokens per session scan A b63485b20ef2

Subscribe to this mod's changes

mcp-atlassian AGENTS.md is an instructions file published in the GitHub repository voarsh2/mcp-atlassian (0 stars, last pushed 4mo 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 94% identical to mcp-atlassian AGENTS.md, differing in 1 line, and is treated as a copy.

Related

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

microsoft/vscode · 6,785 tokens

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.

github/spec-kit · 7,104 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,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

next.js 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