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 aAAaqwq/AGI-Super-Team --skill bitbucket-automationgit clone --depth 1 https://github.com/aAAaqwq/AGI-Super-TeamWrote 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/aaaaqwq/agi-super-team/bitbucket-automation)<a href="https://agentmods.dev/skills/aaaaqwq/agi-super-team/bitbucket-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/bitbucket-automation/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/aaaaqwq/agi-super-team/bitbucket-automation"><img src="https://agentmods.dev/badge/skills/aaaaqwq/agi-super-team/bitbucket-automation.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.00038 | $0.03165 |
| Opus 5 | $0.00019 | $0.01582 |
| Sonnet 5 | $0.00008 | $0.00633 |
| Haiku 4.5 | $0.00004 | $0.00316 |
Grade A, and why
bitbucket-automation 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.
This is a copy
100% identical to bitbucket-automation — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket Automation via Rube MCP
Automate Bitbucket operations including repository management, pull request workflows, branch operations, issue tracking, and workspace administration through Composio's Bitbucket toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active Bitbucket connection via
RUBE_MANAGE_CONNECTIONSwith toolkitbitbucket - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkitbitbucket - If connection is not ACTIVE, follow the returned auth link to complete Bitbucket OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Manage Pull Requests
When to use: User wants to create, review, or inspect pull requests
Tool sequence:
BITBUCKET_LIST_WORKSPACES- Discover accessible workspaces [Prerequisite]BITBUCKET_LIST_REPOSITORIES_IN_WORKSPACE- Find the target repository [Prerequisite]BITBUCKET_LIST_BRANCHES- Verify source and destination branches exist [Prerequisite]BITBUCKET_CREATE_PULL_REQUEST- Create a new PR with title, source branch, and optional reviewers [Required]BITBUCKET_LIST_PULL_REQUESTS- List PRs filtered by state (OPEN, MERGED, DECLINED) [Optional]BITBUCKET_GET_PULL_REQUEST- Get full details of a specific PR by ID [Optional]BITBUCKET_GET_PULL_REQUEST_DIFF- Fetch unified diff for code review [Optional]BITBUCKET_GET_PULL_REQUEST_DIFFSTAT- Get changed files with lines added/removed [Optional]
Key parameters:
workspace: Workspace slug or UUID (required for all operations)repo_slug: URL-friendly repository namesource_branch: Branch with changes to mergedestination_branch: Target branch (defaults to repo main branch if omitted)reviewers: List of objects withuuidfield for reviewer assignmentstate: Filter for LIST_PULL_REQUESTS -OPEN,MERGED, orDECLINEDmax_chars: Truncation limit for GET_PULL_REQUEST_DIFF to handle large diffs
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 · 225 lines · 38 tokens per session scan A 95410a40df4c
bitbucket-automation is a skill published in the GitHub repository aAAaqwq/AGI-Super-Team (92 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 3,165 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to bitbucket-automation, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".
do
Work an increment task by task through the ledger: task next, claim, implement, commit, task done with evidence. Use when saying "implement", "start working", or "continue increment".
triage
Triage a GitHub repository's open issues by finding exact duplicates, rejecting evidenceably off-base requests, requesting concrete clarification, applying only existing labels, and opening a linked root-cause issue when multiple reports share one underlying invariant failure. Use when a maintainer asks to triage…
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…