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 GGGODLIN/claude-pr-review --skill bitbucket-pr-reviewgit clone --depth 1 https://github.com/GGGODLIN/claude-pr-reviewWrote 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/gggodlin/claude-pr-review/bitbucket-pr-review)<a href="https://agentmods.dev/skills/gggodlin/claude-pr-review/bitbucket-pr-review"><img src="https://agentmods.dev/badge/skills/gggodlin/claude-pr-review/bitbucket-pr-review/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/gggodlin/claude-pr-review/bitbucket-pr-review"><img src="https://agentmods.dev/badge/skills/gggodlin/claude-pr-review/bitbucket-pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 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 20 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 Rogue Agent · line 39 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 39 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00087 | $0.04860 |
| Opus 5 | $0.00044 | $0.02430 |
| Sonnet 5 | $0.00017 | $0.00972 |
| Haiku 4.5 | $0.00009 | $0.00486 |
Grade A, and why
bitbucket-pr-review 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 13d 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.
> ⚠️ **本檔在契約測試底下**:`skills/bitbucket-pr-mutation/scripts/tests/test_no_raw_bitbucket_writes.py` 會讀本檔做內容斷言,並掃描全檔有無 raw curl POST/PUT/DELETE。改完跑: How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitbucket PR Review
⚠️ 本檔在契約測試底下:
skills/bitbucket-pr-mutation/scripts/tests/test_no_raw_bitbucket_writes.py會讀本檔做內容斷言,並掃描全檔有無 raw curl POST/PUT/DELETE。改完跑:cd <repo-root>/skills/bitbucket-pr-mutation/scripts && python3 -m unittest discover -s tests -q
Inspect Bitbucket Cloud pull request evidence through read-only REST API calls.
完整 PR review 請改用 /pr-review。本 skill 只處理既有 finding、留言、作者回覆、diff 位置或 PR 證據的定點複查,不產出正式 review 報告,也不派報告 auditor。
Config
- Workspace:
$BITBUCKET_WORKSPACE(the Bitbucket workspace slug, e.g.your-workspace) - Email:
$BITBUCKET_EMAIL— your Atlassian account email - Token: Scoped API token exported as
BITBUCKET_API_TOKEN - API Base:
https://api.bitbucket.org/2.0
Authentication
Step 0 — ALWAYS use bb_api.sh, NEVER raw curl with hand-crafted auth. The helper handles token loading + Basic Auth + 302 redirects (-sL) in one place. Raw curl with manual -u flags has caused repeated 401s + diff-endpoint-returns-empty bugs.
bash <skill_dir>/scripts/bb_api.sh "<endpoint>"
That's it for read endpoints. Do not paste your own curl -u ... even "just to test"—the failure modes (401 / empty diff / wrong account) are the exact bugs this skill exists to prevent.
Background (only relevant when bb_api.sh itself misbehaves)
bb_api.shreadsBITBUCKET_API_TOKENandBITBUCKET_EMAILenv-first, then falls back to grepping the shell secrets files listed inBITBUCKET_SECRETS_FILES(default~/.zsh_secretsthen~/.zshrc— adjust that list to wherever your own setup keeps exported secrets). Sourcing the rc file instead is not an option: interactive-only rc files routinely fail under non-interactive shells (nvm / compdef / prompt-init errors).- 🪤 If you see
ERROR: BITBUCKET_API_TOKEN not in env or in: ..., the token is genuinely unreadable — that is NOT the same as the token being expired. Runecho ${#BITBUCKET_API_TOKEN}first: a non-zero length means the credential is alive and only the read path is broken. Moving the token between secrets files while helpers still grep the old one produces exactly this error and is repeatedly misdiagnosed as an expired token. - Atlassian killed Bitbucket app passwords (CHANGE-3222, returns 410). Anything still using the older username + app password pair is dead; only account email + scoped API token works for REST.
- For git push/pull over HTTPS the same token uses a different username (
x-bitbucket-api-token-auth), not your account email.
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.
- 13d ago First seen · 245 lines · 87 tokens per session scan A 608c3b9ce79d
bitbucket-pr-review is a skill published in the GitHub repository GGGODLIN/claude-pr-review (114 stars, last pushed yesterday), licensed MIT. It adds 87 tokens to every session and 4,860 once invoked, about $0.0004 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
full-repo-review
Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…