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 restarter/lets-workflow --skill loop-bb-prgit clone --depth 1 https://github.com/restarter/lets-workflowWrote 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/restarter/lets-workflow/loop-bb-pr)<a href="https://agentmods.dev/skills/restarter/lets-workflow/loop-bb-pr"><img src="https://agentmods.dev/badge/skills/restarter/lets-workflow/loop-bb-pr/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/restarter/lets-workflow/loop-bb-pr"><img src="https://agentmods.dev/badge/skills/restarter/lets-workflow/loop-bb-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.02004 |
| Opus 5.5 | $0.00047 | $0.00802 |
| Sonnet 5.5 | $0.00024 | $0.00401 |
| Haiku 4.5 | $0.00012 | $0.00200 |
Grade A, and why
loop-bb-pr 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 1mo 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.
│ (curl fallback planned for v1.1.) │ How it starts
The opening of the file, as written. The whole thing — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
loop-bb-pr
Compose a /loop that periodically polls a Bitbucket PR via the bb-api wrapper and surfaces changes (new comments, review state, merge, decline).
The skill never invokes /loop itself at initial start — Claude Code's /loop is a UI command. It composes the prompt and presents for paste; once active, the autonomous run uses ScheduleWakeup directly per tick (that part is model-callable).
IMPORTANT: If the spec below invokes any deferred tool (e.g.
AskUserQuestion), you MUST load and call it as specified.
Step 1: Resolve PR URL
Parse args parameter for URL. If not provided, AskUserQuestion:
AskUserQuestion(
questions=[{
question: "Bitbucket PR URL to watch?",
header: "PR URL",
options: [
{ label: "I'll paste it", description: "Send the bitbucket.org/.../pull-requests/N URL in your next message" },
{ label: "Cancel", description: "Abort composition" }
],
multiSelect: false
}]
)
If user picks "I'll paste it", wait for URL in their next message.
Normalize then validate — real BB URLs often have query strings (?at=branch&type=...) or trailing slashes. Strip before regex match:
URL="<from input>"
URL="${URL%%\?*}" # strip query string (everything from ? onward)
URL="${URL%#*}" # strip fragment (everything from # onward)
URL="${URL%/}" # strip trailing slash
Then strict validation — normalized URL must match exactly:
^https://bitbucket\.org/[a-zA-Z0-9_-]+/[a-zA-Z0-9_.-]+/pull-requests/[0-9]+$
If validation fails: surface error, exit. Do NOT proceed with malformed URL — the composed prompt may persist (if user switches to interval mode in v1.1) and we don't want arbitrary input in .claude/scheduled_tasks.json.
Extract via regex or sed (from normalized URL):
WORKSPACE— first segment afterbitbucket.org/REPO— second segmentPR_ID— final numeric segment
Step 2: Verify bb-api availability
which bb-api 2>/dev/null
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.
- 1mo ago First seen · 173 lines · 118 tokens per session scan A 2791feb6f896
loop-bb-pr is a skill published in the GitHub repository restarter/lets-workflow (17 stars, last pushed today), licensed MIT. It adds 118 tokens to every session and 2,004 once invoked, about $0.0005 per session on Opus 5.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
fix
Read this repo's open issues, triage them, and open one pull request per issue that can be fixed without a judgement call. Issues that need a decision, or that look stale or superseded, are reported with a recommendation rather than guessed at.
watch-pr
Watch a GitHub pull request for CI status, reviews, comments, merge conflicts, and terminal states using the gh-watch extension. Use when the user wants to monitor a PR, wait for CI, or track PR progress.
diff-summary
Structured triage of a git diff. One call replaces the per-file Read sweep an agent normally does to figure out which files in a diff are tests, which touch the public API, which are migrations, which need careful review.
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.