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 synthesisengineering/synthesis-skills --skill synthesis-bitbucketgit clone --depth 1 https://github.com/synthesisengineering/synthesis-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/synthesisengineering/synthesis-skills/synthesis-bitbucket)<a href="https://agentmods.dev/skills/synthesisengineering/synthesis-skills/synthesis-bitbucket"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-bitbucket/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/synthesisengineering/synthesis-skills/synthesis-bitbucket"><img src="https://agentmods.dev/badge/skills/synthesisengineering/synthesis-skills/synthesis-bitbucket.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 53 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 58 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00118 | $0.01557 |
| Opus 5 | $0.00059 | $0.00779 |
| Sonnet 5 | $0.00024 | $0.00311 |
| Haiku 4.5 | $0.00012 | $0.00156 |
Grade A, and why
synthesis-bitbucket scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **One command surface.** Do not mix `bkt`, raw `curl`, and git-host web UIs in one workflow — state drifts and auth surfaces multiply. How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Synthesis Bitbucket (via bkt)
How an agent interacts with Bitbucket Cloud using bkt, an open-source community CLI that fills the role gh plays for GitHub. This skill exists because agents working across many repos otherwise drift to raw REST calls or the wrong CLI, reassembling auth, URL-encoding, and pagination by hand — differently every session.
The rule in one line: if bkt can do it, use bkt. The REST API is the escape hatch (bkt api), not the default.
Teams layer a private companion skill on top of this one carrying their workspace names, default context, and release conventions. This skill stays generic.
Install and pin
brew install avivsinai/tap/bitbucket-cli
brew pin bitbucket-cli # freeze at the installed version
bkt --version
Pin a reviewed version. bkt is a community tool with write access to your repos. Review a release (or adopt your team's reviewed version), pin it, and re-review the diff before upgrading. brew pin freezes whatever is installed; a checksummed release binary from the project's GitHub Releases page is the alternative when you need an exact older version.
Authenticate
Preferred — OAuth in the browser (no token handling):
bkt auth login https://bitbucket.org --kind cloud --web
Alternative — scoped API token created under the Bitbucket application at id.atlassian.com → Security → API tokens:
bkt auth login https://bitbucket.org --kind cloud \
--username <atlassian-account-email> --token <api-token>
The username is the email of the Atlassian account that owns the token — not a Bitbucket username. Prefer the interactive prompt over --token (flags leak into shell history and process listings). Credentials land in the OS keychain.
⚠️ Scoped API tokens that authenticate the REST API do not necessarily authenticate the git HTTPS endpoint — they are separate credential surfaces. For git push/fetch, use SSH keys; keep bkt on the token. Mixing the two surfaces produces "the token works here but not there" mysteries that look like access problems and are not.
What ships with it
1 file 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.
- 10d ago First seen · 105 lines · 118 tokens per session scan A 9148cfd1ab1c
synthesis-bitbucket is a skill published in the GitHub repository synthesisengineering/synthesis-skills (18 stars, last pushed today), licensed Apache-2.0. It adds 118 tokens to every session and 1,557 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.