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 skills/openhands/extensions/bitbucketnpx skills add OpenHands/extensions --skill bitbucketgit clone --depth 1 https://github.com/OpenHands/extensionsWhat 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.00052 | $0.00609 |
| Opus 5 | $0.00026 | $0.00304 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
bitbucket 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.
What it actually says
You are working with Bitbucket, which ships as two distinct products that behave differently:
- Bitbucket Cloud (
bitbucket.org) — authenticates with theBITBUCKET_TOKENenvironment variable. - Bitbucket Data Center (self-hosted Bitbucket Server) — authenticates with the
BITBUCKET_DATA_CENTER_TOKENenvironment variable.
They use different REST APIs, repository identifiers, git remote URL formats, and pull request tools, so you must first determine which one you are on, then load the matching detailed skill for full instructions.
Step 1 — Detect which Bitbucket you are on
Check which token environment variable is present. Environment variable names are case-sensitive, so look for it case-insensitively:
env | grep -i 'bitbucket' || echo "no bitbucket token found"
- If a
BITBUCKET_DATA_CENTER_TOKENvariable is set (in any letter case) → you are on Bitbucket Data Center. - Otherwise, if a
BITBUCKET_TOKENvariable is set → you are on Bitbucket Cloud. - If neither is set, ask the user how they authenticate to Bitbucket before proceeding.
When you reference the token later, use the exact variable name (and letter case) that actually exists in the environment.
Step 2 — Load the detailed skill
Once you know the environment, use the invoke_skill tool to load the matching skill for
full instructions on API calls, authenticated git remotes, and opening pull requests:
- Bitbucket Cloud → invoke the
bitbucket-cloudskill. - Bitbucket Data Center → invoke the
bitbucket-data-centerskill.
Quick reference (fallback)
If you are unable to load the detailed skill, these are the essentials. Always use the Bitbucket API (not a web browser) and always use the listed PR tool to open a pull request.
| Bitbucket Cloud | Bitbucket Data Center | |
|---|---|---|
| Token env var | BITBUCKET_TOKEN |
BITBUCKET_DATA_CENTER_TOKEN |
| Host | bitbucket.org |
self-hosted domain |
| REST API base | https://api.bitbucket.org/2.0 |
https://<host>/rest/api/1.0 |
| Repository identifier | workspace/repo_slug |
PROJECT/repo_slug (project key) |
| Pull request tool | create_bitbucket_pr |
create_bitbucket_data_center_pr |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 56 lines · 52 tokens per session scan A b9c7fb63cef3
bitbucket is a skill published in the GitHub repository OpenHands/extensions (137 stars, last pushed 4d ago), licensed MIT. It adds 52 tokens to every session and 609 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…