What is atlassian-server-mcp AGENTS.md?

Project instructions for an Atlassian server MCP, a service that connects AI tools with Jira, Confluence, and Bitbucket. They describe which files are generated and how to update operation definitions, policies, test coverage, and release evidence.

Use them when changing Jira, Confluence, or Bitbucket operations, updating exposure rules, refreshing approved API snapshots, generating coverage data, or reconciling end-to-end test results.

They prevent manual edits to generated files and keep code, policy, tests, and evidence synchronized through the project's scripts.

How zaimokuza-yoshiteru/atlassian-server-mcp configures Codex and Open

Reuse

Borrowing it

Nothing to install: this file belongs to zaimokuza-yoshiteru/atlassian-server-mcp. 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/zaimokuza-yoshiteru/atlassian-server-mcp/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/zaimokuza-yoshiteru/atlassian-server-mcp

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

Your own site

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

Per session 2,031 This file is loaded in full into every session.

When invoked 2,031 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.02031	$0.02031
Opus 5	$0.01015	$0.01015
Sonnet 5	$0.00406	$0.00406
Haiku 4.5	$0.00203	$0.00203

Measured 10d ago against content hash 4faef29110a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

atlassian-server-mcp 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 10d 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.

AGENTS.md · 90 lines

How it starts

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

Agent Conventions

Generated files

src/operations/jira.ts, src/operations/confluence.ts, src/operations/bitbucket.ts are generated by scripts/generate-operations.mjs. Never hand-edit them.
src/operations/registry.json is generated by the same generator. Never hand-edit it; use node scripts/generate-operations.mjs.
src/exposure-policy.json is generated by rule/build-policy.mjs. Never hand-edit it; update rule/source.md and run the policy builder.
To change an operation manifest, edit the OVERRIDES array in scripts/generate-operations.mjs and regenerate.
rule/spec-cache/ and its manifest are committed canonical official snapshots. Refresh only with explicit node rule/fetch-api-inventory.mjs --refresh --bootstrap or reviewed --refresh --accept-drift; ordinary checks are offline and must not update mtimes or provenance.
tests/e2e/coverage.json is generated by scripts/generate-e2e-coverage.mjs. Update the automated map and run pnpm coverage:generate.

E2E operation-level reconciliation

scripts/e2e-reconcile.mjs cross-references the coverage ledger against the vitest JSON report and the invoked-ops journal. Verdicts:

PASS: at least one invocation where expectError === isError (both true for error-contract tests, both false for success-expected calls).
PARTIAL: the scenario has a failing it() OR the op was invoked but no invocation matched its expected outcome.
NOT RUN: the scenario is absent from the vitest report, or the suite passed but the op was never invoked.

Reconcile exits non-zero on any PARTIAL or NOT RUN. pnpm e2e:jira must not be committed against a non-zero reconcile.

Run evidence chain

scripts/e2e.mjs writes .e2e-state/<product>/run-manifest.json at run start (gitSha, dirty plus truncated dirtyFiles, startedAt, product, dockerImageDigest, probed productVersion, coverageSha of tests/e2e/coverage.json, policySha of src/exposure-policy.json) and embeds the same fields into .e2e-state/<product>/run-report.json, making the report self-contained. Starting a run deletes that product's previous report and manifest; other products' state directories are left untouched.

Read the full file on GitHub · 90 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.

10d ago First seen · 90 lines · 2,031 tokens per session scan A 4faef29110a1

Subscribe to this mod's changes

atlassian-server-mcp AGENTS.md is an instructions file published in the GitHub repository zaimokuza-yoshiteru/atlassian-server-mcp (1 stars, last pushed 24d ago), licensed MIT. It adds 2,031 tokens to every session, about $0.0102 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.

atlassian bitbucket confluence data-center jira jira-data-center

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

atlassian-server-mcp: Instructions file for Codex