Borrowing it
Nothing to install: this file belongs to or2ooo/bitbucket-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.
curl -O https://raw.githubusercontent.com/or2ooo/bitbucket-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/or2ooo/bitbucket-mcpWrote 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/or2ooo/bitbucket-mcp/claude-md)<a href="https://agentmods.dev/instructions/or2ooo/bitbucket-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/or2ooo/bitbucket-mcp/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.00665 | $0.00665 |
| Opus 5 | $0.00332 | $0.00332 |
| Sonnet 5 | $0.00133 | $0.00133 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
bitbucket-mcp 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 6d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket Cloud MCP Server
MCP server for Bitbucket Cloud REST API v2.0. Works with any MCP client.
Quick Reference
npm run build # Compile TypeScript → dist/
npm run start # Run the MCP server (requires env vars)
npm test # Run tests with vitest
npm run lint # ESLint check
Environment Variables
| Variable | Required | Description |
|---|---|---|
ATLASSIAN_USER_EMAIL |
Yes | Atlassian account email |
ATLASSIAN_API_TOKEN |
Yes | Atlassian API token (app password) |
BITBUCKET_DEFAULT_WORKSPACE |
No | Default workspace when not specified in tool calls |
BITBUCKET_ALLOWED_WORKSPACES |
No | Comma-separated allowlist of workspace slugs |
BITBUCKET_ALLOWED_REPOS |
No | Comma-separated allowlist (slug or workspace/slug) |
BITBUCKET_READONLY |
No | Set to true to block all write operations |
BITBUCKET_BASE_URL |
No | Override API base URL (default: https://api.bitbucket.org/2.0) |
Project Structure
src/
├── index.ts # Entry point — MCP server setup + transport
├── config.ts # Environment variable parsing
├── safety.ts # Access control guards
├── formatting.ts # LLM-optimized output formatters
├── bitbucket/
│ ├── types.ts # Bitbucket API type definitions
│ └── client.ts # HTTP client with auth + pagination
└── toolsets/
├── context.ts # bb_whoami, bb_list_workspaces
├── repos.ts # Repository & file tools
├── pullRequests.ts # PR tools (list, create, diff, merge, etc.)
├── issues.ts # Issue tracker tools
└── pipelines.ts # CI/CD pipeline tools
Module Boundaries
- config.ts: Only env var parsing. No API calls.
- client.ts: HTTP only. No formatting or safety logic.
- safety.ts: Pure validation. No side effects.
- formatting.ts: String formatting only. No API calls.
- toolsets/: Each file registers tools on a McpServer. Depends on client, config, safety, formatting.
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.
- 6d ago First seen · 70 lines · 665 tokens per session scan A 81c23b18d6bd
bitbucket-mcp CLAUDE.md is an instructions file published in the GitHub repository or2ooo/bitbucket-mcp (2 stars, last pushed 5mo ago), licensed MIT. It adds 665 tokens to every session, about $0.0033 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
plan-forge dapr.instructions.md
Dapr patterns for .NET — building blocks, component config, sidecar architecture, multi-tenant isolation, workflows, state management, secrets.
plan-forge caching.instructions.md
Caching patterns for .NET — IDistributedCache, Redis, in-memory, cache-aside, TTL strategies.
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.
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).
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).