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 avivsinai/skills-marketplace --skill bktgit clone --depth 1 https://github.com/avivsinai/skills-marketplaceWrote 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/avivsinai/skills-marketplace/bkt)<a href="https://agentmods.dev/skills/avivsinai/skills-marketplace/bkt"><img src="https://agentmods.dev/badge/skills/avivsinai/skills-marketplace/bkt/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/avivsinai/skills-marketplace/bkt"><img src="https://agentmods.dev/badge/skills/avivsinai/skills-marketplace/bkt.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.00049 | $0.00958 |
| Opus 5 | $0.00024 | $0.00479 |
| Sonnet 5 | $0.00010 | $0.00192 |
| Haiku 4.5 | $0.00005 | $0.00096 |
Grade A, and why
bkt 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 5d 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 bkt — 0 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket CLI (bkt)
Use bkt for Bitbucket Cloud and Data Center operations. Prefer structured
--json, --yaml, --jq, or --template output for automation.
Start with the requested operation
Run bkt --version only when installation or compatibility is uncertain. Run
bkt auth status when the command needs authentication or the active platform
and context are unknown. Do not make setup a prerequisite for an already
configured read-only request.
Cloud and Data Center have different feature sets. Determine the platform from the active context or ask when it cannot be inferred. Do not suggest a Cloud-only command for Data Center, or the reverse.
Read setup and common workflows when installing, authenticating, creating a context, or learning the main command patterns. For config-free CI or containers, read headless authentication.
Route to the command reference
Read only the reference for the requested command group:
- pull requests, repositories, branches, commits, or statuses
- Cloud issues, pipelines, or variables
- Data Center administration, projects, or permissions
- authentication, contexts, webhooks, extensions, MCP, skills, or raw API
Mutation and credential boundaries
- Listing, viewing, status, and checks are read-only. Create, edit, approve, merge, delete, rerun, or permission changes modify Bitbucket; perform them only when the user requested that change.
- Never place tokens, OAuth secrets, or passwords in commands that could enter logs or committed files. Use the CLI's supported credential flow or environment variables described in the auth references.
- Official release binaries embed the Cloud browser-OAuth consumer credentials.
Do not remove that behavior as generic hardening. Source and Nix builds may
require
BKT_OAUTH_CLIENT_IDandBKT_OAUTH_CLIENT_SECRET. - Before a merge or other consequential write, inspect the exact target, repository, and current checks. Report the resulting URL or identifier.
What ships with it
20 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.
- rules/admin.md 5.3 KB
- rules/auth.md 7.4 KB
- rules/branch.md 13 KB
- rules/commit.md 2.2 KB
- rules/context.md 5.0 KB
- rules/extension.md 5.3 KB
- rules/guide.md 5.8 KB
- rules/headless.md 3.2 KB
- rules/issue.md 17 KB
- rules/mcp.md 29 KB
- rules/other.md 1.2 KB
- rules/perms.md 11 KB
- rules/pipeline.md 7.6 KB
- rules/pr.md 45 KB
- rules/project.md 4.2 KB
- rules/repo.md 11 KB
- rules/skill.md 17 KB
- rules/status.md 5.9 KB
- rules/variable.md 7.6 KB
- rules/webhook.md 6.7 KB
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.
- 5d ago Changed · -98 lines · -29 tokens per session 800be3b2ea71
- 7d ago Changed · +15 lines 94f3ced45e53
- 12d ago First seen · 166 lines · 78 tokens per session scan A 4dc3a116fe91
bkt is a skill published in the GitHub repository avivsinai/skills-marketplace (2 stars, last pushed today), licensed MIT. It adds 49 tokens to every session and 958 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 bkt, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
artifact-metadata
Manage artifact metadata, versioning, ownership, and review history across the SDLC lifecycle.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
steward-prep-delivery
Steward-assisted prep for filing issues and PRs — environment capture, template selection, duplicate detection, delivery-policy compliance check.
contribute-start
Initialize an AIWG contribution workflow by creating a feature branch, configuring DCO, and linking a tracking issue.
ijfw-ship
Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…
workspace
Multi-repo workspace coordinator for shared team context. Initialize .adlc/ structure, configure .gitignore, discover child repos, link them as Git submodules, and audit workspace health. Use --init for first-time setup, default mode for ongoing auditing.