Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
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.
[](https://agentmods.dev/instructions/tugudush/bitbucket-mcp/copilot-instructions)<a href="https://agentmods.dev/instructions/tugudush/bitbucket-mcp/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/tugudush/bitbucket-mcp/copilot-instructions.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.05428 | $0.05428 |
| Opus 5 | $0.02714 | $0.02714 |
| Sonnet 5 | $0.01086 | $0.01086 |
| Haiku 4.5 | $0.00543 | $0.00543 |
Grade A, and why
bitbucket-mcp copilot-instructions.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 5d 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 — 557 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket MCP Server - AI Coding Instructions
Architecture Overview
This is a Model Context Protocol (MCP) server providing read-only access to Bitbucket API v2.0. The architecture follows a modular pattern with clear separation of concerns:
- TypeScript interfaces - Strict typing for all Bitbucket API responses
- Zod schemas - Input validation using
z.object()with descriptive field documentation - Tool registration - Each tool uses
zodToJsonSchema()for automatic schema generation - Handler registry pattern - Modular domain-based handlers (replaces switch-case)
- Authentication system - Supports API tokens
- Branch handling - Uses
?at=branchfor listings and/src/{ref}/{file}for file content - Read-only by design - All operations are safe GET requests
Enhanced Features (2025-2026 Update)
Modular Architecture
src/index.ts- Main MCP server entry pointsrc/tools.ts- Tool definitions and handler registry routingsrc/handlers/- Domain-specific tool handlers (repository, pullrequest, diff, etc.)src/handlers/index.ts- Central handler registry exportsrc/handlers/types.ts- Shared handler interfacessrc/config.ts- Configuration management with Zod validationsrc/errors.ts- Custom error classes with helpful suggestionssrc/api.ts- API layer with retry logic and dual response typessrc/types.ts- Comprehensive TypeScript interfacessrc/schemas.ts- Centralized Zod schemas and API constants
Authentication & Security
- API Token Priority: Uses
BITBUCKET_API_TOKEN+BITBUCKET_EMAIL - Runtime Protection: Blocks non-GET requests at the
makeRequest()level - Configuration Validation: Type-safe environment variable parsing with error suggestions
Handler Registry Pattern (2025-2026)
Replaced large switch statements with modular, domain-based handlers:
// src/handlers/index.ts - Central registry
export const toolHandlers: Record<string, ToolHandler> = {
bb_get_repository: handleGetRepository,
bb_list_repositories: handleListRepositories,
bb_get_pull_requests: handleGetPullRequests,
// ... 38 total tools organized by domain
};
// src/tools.ts - Clean lookup pattern
export async function handleToolCall(request: CallToolRequest) {
const { name, arguments: args } = request.params;
const handler = toolHandlers[name];
return handler ? await handler(args) : errorResponse;
}
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.
- 5d ago First seen · 557 lines · 5,428 tokens per session scan A da29976fc708
bitbucket-mcp copilot-instructions.md is an instructions file published in the GitHub repository tugudush/bitbucket-mcp (4 stars, last pushed 1mo ago), licensed MIT. It adds 5,428 tokens to every session, about $0.0271 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
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).
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 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).
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.
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.
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.