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 skills add abdullahkhawer/devops-skills --skill bitbucket-cligit clone --depth 1 https://github.com/abdullahkhawer/devops-skillsWrote 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/skills/abdullahkhawer/devops-skills/bitbucket-cli)<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/bitbucket-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/bitbucket-cli/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.
<a href="https://agentmods.dev/skills/abdullahkhawer/devops-skills/bitbucket-cli"><img src="https://agentmods.dev/badge/skills/abdullahkhawer/devops-skills/bitbucket-cli.svg" alt="Reviewed on agentmods" width="80" 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.00066 | $0.01212 |
| Opus 5.5 | $0.00026 | $0.00485 |
| Sonnet 5.5 | $0.00013 | $0.00242 |
| Haiku 4.5 | $0.00007 | $0.00121 |
Grade B, and why
bitbucket-cli scanned grade B with 2 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 23d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
mkdir -p ~/.bitbucket && echo "<username>:<app-password>" > ~/.bitbucket/token && chmod 600 ~/.bitbucket/token Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
description: Perform Bitbucket operations using the Bitbucket REST API via curl. Use for repositories, pull requests, pipelines, and issues. ALSO use this skill when asked to review a Bitbucket PR — when a Bitbucket PR U How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket CLI Skill
Bitbucket Cloud has no official first-party CLI equivalent to gh/glab — use the REST API via curl for all operations.
Configuration
Update the workspace below before using this skill:
| Setting | Value |
|---|---|
| Bitbucket Workspace | <your-workspace> |
| Credential File | ~/.bitbucket/token |
If the target workspace is unclear, ask the user before running any command.
Prerequisites (one-time setup by user)
Create an App Password with Repositories: Read (and Write/Pull requests: Write if mutations are needed), then save <username>:<app-password> to the credential file. Never print or display the credential value. Do not perform these steps yourself.
mkdir -p ~/.bitbucket && echo "<username>:<app-password>" > ~/.bitbucket/token && chmod 600 ~/.bitbucket/token
Command Format
All API calls use curl with basic auth read from the credential file:
curl -s -u "$(cat ~/.bitbucket/token)" \
"https://api.bitbucket.org/2.0/<endpoint>" | jq .
PR Code Review
When asked to review a Bitbucket PR (URL or PR ID provided), extract the <workspace/repo> and <PR_ID> from the URL (ask the user if the repo is missing), then fetch the PR metadata (GET /2.0/repositories/<workspace>/<repo>/pullrequests/<PR_ID>) and its diff (GET /2.0/repositories/<workspace>/<repo>/pullrequests/<PR_ID>/diff). To fully understand the context and impact of all code changes, read the complete source branch codebase — the diff alone does not capture the surrounding logic, dependencies, or broader design that the changes interact with. Report the PR title, author, and branches, then review all changed files for: secrets/injection/XSS (security), inefficient algorithms/memory leaks (performance), code smells/dead code (quality), missing error handling, excessive or sensitive logging, and missing/outdated documentation. For each finding, include the file path, line number(s), the problematic snippet, and a suggested fix. If nothing is wrong, summarize what was reviewed and state it looks good.
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.
- 23d ago First seen · 84 lines · 66 tokens per session scan B 2c79d33850ea
bitbucket-cli is a skill published in the GitHub repository abdullahkhawer/devops-skills (8 stars, last pushed 24d ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,212 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-23.
Other skills, from other repositories
github-code-review
Comprehensive GitHub code review with AI-powered swarm coordination.
ci-cd
CI/CD pipelines for GitHub Actions and Docker-based deployments — lint, test, build, push, deploy stages; environment secrets; branch-gated workflows; health-check rollbacks; and PM2/systemd service restarts.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
gentle-ai-collab-perfect
Trigger: contributing to Gentleman-Programming/gentle-ai as an external collaborator. Strict issue-first workflow, honest PR bodies, contributor-vs-maintainer scope, chained-PR strategy, verification protocol, docstring coverage. Load whenever the active repo is Gentleman-Programming/gentle-ai and any part of the…
branch-pr
Create Gentle AI pull requests with issue-first checks. Trigger: creating, opening, or preparing PRs for review.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.