bitbucket-cli: Instructions file for Claude Code

CLAUDE.md

bitbucket-cli CLAUDE.md is an instructions file for Claude Code from avivsinai/bitbucket-cli. It costs 857 tokens per session, scanned A, original, MIT.

Repository instructions for bitbucket-cli, a Go command-line program for working with Bitbucket. They describe its folders, build and test commands, coding conventions, and Windows support.

In plain words
What is it for?
Use them when modifying commands or packages, running builds and tests, formatting Go code, updating dependencies, or checking that changes work on supported Windows and other environments.
Why use it?
They give a coding agent the project rules and validation steps needed to make changes without placing code in the wrong module or skipping required checks.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions AGENTS.md; mentions Codex.

This is avivsinai/bitbucket-cli's own configuration. It tells Claude Code how to work on bitbucket-cli itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bitbucket-cli configures →

Reuse

Borrowing it

Nothing to install: this file belongs to avivsinai/bitbucket-cli. 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/avivsinai/bitbucket-cli/master/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/avivsinai/bitbucket-cli

Made for: Claude Code.

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 bitbucket-cli CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/avivsinai/bitbucket-cli/claude-md/github.svg)](https://agentmods.dev/instructions/avivsinai/bitbucket-cli/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/avivsinai/bitbucket-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/avivsinai/bitbucket-cli/claude-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.

agentmods 80×15 button for bitbucket-cli CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/avivsinai/bitbucket-cli/claude-md"><img src="https://agentmods.dev/badge/instructions/avivsinai/bitbucket-cli/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 857 This file is loaded in full into every session.
When invoked 857 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00857 $0.00857
Opus 5.5 $0.00343 $0.00343
Sonnet 5.5 $0.00171 $0.00171
Haiku 4.5 $0.00086 $0.00086

Measured 2d ago against content hash 8c9818c40d9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bitbucket-cli 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 2d 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.

CLAUDE.md · 64 lines

How it starts

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

bitbucket-cli

This is the master agent instruction file for this repository. Keep repository policy here. AGENTS.md exists only as a Codex compatibility shim and should contain only Codex-specific notes.

Project Structure & Module Organization

  • cmd/bkt/ contains the CLI entry point; the binary executes internal/bktcmd.
  • internal/ hosts non-exported wiring, including configuration (internal/config) and build metadata.
  • pkg/ holds reusable packages consumed by Cobra commands such as pkg/cmd/repo and pkg/bbdc.
  • Tests live alongside Go packages; add _test.go files next to the implementation.

Build, Test, and Development Commands

  • make build compiles the CLI with go build ./cmd/bkt.
  • make test or go test ./... runs the full unit test suite.
  • make fmt formats the codebase with go fmt ./....
  • make tidy syncs module dependencies with go mod tidy.
  • go run ./cmd/bkt --help is the quick local smoke test.
  • Windows-native development is supported: the same Make targets run under GNU Make with cmd.exe-pinned recipes, and the build-windows CI job is the source of truth for what works on Windows.

Coding Style & Naming Conventions

  • Follow standard Go conventions: tabs for indentation, PascalCase for exported identifiers, camelCase for private helpers.
  • Keep package names short and lowercase; command packages live under pkg/cmd/<topic>.
  • Prefer contextual errors such as fmt.Errorf("action: %w", err).
  • Run go fmt before committing; add comments only when the logic is not obvious.

Testing Guidelines

  • Prefer table-driven tests in _test.go files named Test<Subject>.
  • Use golden files under testdata/ when CLI output snapshots add value.
  • Cover flag parsing, API adapters, and error paths; mock HTTP interactions where needed.
  • Use go test ./pkg/... for faster package-focused iteration.

Release Contract

  • Release from master only through ./scripts/release.sh X.Y.Z and the resulting release PR; do not create manual tags or GitHub releases.
  • A push to master updates the AvivSinai marketplace immediately for the bkt skill.
  • Keep CHANGELOG.md and skill/plugin metadata on one version in the release commit; after the release PR merges, CI validates the merged commit, creates the tag, publishes GitHub/Homebrew artifacts, and uses the committed changelog entry as the GitHub release notes.
  • Bitbucket Cloud browser OAuth (bkt auth login --kind cloud --web) is zero-config in every build — release binaries, Homebrew core, go install, Nix — because bkt's OAuth consumer lives in source (pkg/oauth/cloud.go), as the GitHub CLI and Git Credential Manager ship theirs. A native app's consumer secret is public-client material (RFC 8252 §8.5), not a leak. Moving it out of source or into CI secrets is a breaking auth change (#179 broke it, #190 restored it for release binaries only), never generic hardening. Keep the Bitbucket consumer marked public (no client_credentials grant) and keep the same consumer: refresh tokens are bound to the consumer that issued them.
  • See docs/RELEASE.md for the full release handbook.

Read the full file on GitHub · 64 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. 2d ago Changed · +3 lines · +54 tokens per session 8c9818c40d9d
  2. 1mo ago First seen · 61 lines · 803 tokens per session scan A c9a1dcf88a81

Subscribe to this mod's changes

bitbucket-cli CLAUDE.md is an instructions file published in the GitHub repository avivsinai/bitbucket-cli (247 stars, last pushed today), licensed MIT. It adds 857 tokens to every session, about $0.0034 per session on Opus 5.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-30.

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 · 9,715 tokens

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,581 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens