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/thienntdev/mcp-atlassian/agents-mdgit clone --depth 1 https://github.com/thienntdev/mcp-atlassianWhat 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 | $0.00712 | $0.00712 |
| Opus 5 | $0.00356 | $0.00356 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
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 yesterday.
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.
This is a copy
95% 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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS
Audience: LLM-driven engineering agents
This file provides guidance for autonomous coding agents working inside the MCP Atlassian repository.
Repository map
| Path | Purpose |
|---|---|
src/mcp_atlassian/ |
Library source code (Python ≥ 3.10) |
├─ jira/ |
Jira client, mixins, and operations |
├─ confluence/ |
Confluence client, mixins, and operations |
├─ models/ |
Pydantic data models for API responses |
├─ servers/ |
FastMCP server implementations |
└─ utils/ |
Shared utilities (auth, logging, SSL) |
tests/ |
Pytest test suite with fixtures |
scripts/ |
OAuth setup and testing scripts |
Mandatory dev workflow
uv sync --frozen --all-extras --dev # install dependencies
pre-commit install # setup hooks
pre-commit run --all-files # Ruff + Prettier + Pyright
uv run pytest # run full test suite
Tests must pass and lint/typing must be clean before committing.
Core MCP patterns
Tool naming: {service}_{action} (e.g., jira_create_issue)
Architecture:
- Mixins: Functionality split into focused mixins extending base clients
- Models: All data structures extend
ApiModelbase class - Auth: Supports API tokens, PAT tokens, and OAuth 2.0
Development rules
- Package management: ONLY use
uv, NEVERpip - 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
Code conventions
- Language: Python ≥ 3.10
- Line length: 88 characters maximum
- Imports: Absolute imports, sorted by ruff
- Naming:
snake_casefunctions,PascalCaseclasses - Docstrings: Google-style for all public APIs
- Error handling: Specific exceptions only
Development guidelines
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.
- yesterday First seen · 94 lines · 712 tokens per session scan A 1ef65cf79187
mcp-atlassian AGENTS.md is an instructions file published in the GitHub repository thienntdev/mcp-atlassian (0 stars, last pushed 1y ago), licensed MIT. It adds 712 tokens to every session, about $0.0036 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to mcp-atlassian AGENTS.md, differing in 1 line, and is treated as a copy.
Other instructions, from other repositories
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.
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 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).
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.
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).
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.