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 OAI-Labs/vibe-flow --skill vibe-linkgit clone --depth 1 https://github.com/OAI-Labs/vibe-flowWrote 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/oai-labs/vibe-flow/vibe-link)<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-link"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-link/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/oai-labs/vibe-flow/vibe-link"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-link.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.00041 | $0.01873 |
| Opus 5 | $0.00020 | $0.00937 |
| Sonnet 5 | $0.00008 | $0.00375 |
| Haiku 4.5 | $0.00004 | $0.00187 |
Grade A, and why
vibe-link 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-link
Overview
Bridge between vibe-kanban workspace output (a pushed branch) and GitHub pull requests. Ensures every completed workspace has a tracked PR, and the issue comments reference it.
Core principle: One workspace → one branch → one PR → one issue. Keep the graph tight.
Announce at start: "I'm using the vibe-link skill to link PR to workspace."
When to use
- A workspace just reported
status: completewith a branch pushed - User explicitly invokes
/vibe-flow:vibe-link <workspace_id> - Auto-triggered by
vibe-shipafter each workspace completes
Do NOT use if:
- Workspace is still running (wait for FINAL REPORT)
- Workspace reported
status: blocked(no branch pushed) - Branch already has a PR that's linked in issue comments (idempotent skip)
Required context
workspace_idfrom vibe-kanban- Repo path on disk (to run
ghcommands) ghCLI authenticated with repo access
The process
Step 1: Fetch workspace info
Call MCP get_execution or list_sessions for the workspace. Extract:
branch— prefer the value from the agent's FINAL REPORT. VK workspace metadata also exposes a "working branch" field, but it is VK's internal auto-generated name (sometimes truncated in the UI) and is NOT guaranteed to equal the actual branch the agent pushed toorigin. Trust the FINAL REPORT first; fall back to VK metadata only if FINAL REPORT is missing.issue_id(from workspace link)commit_sha(from FINAL REPORT)
Verify branch exists on origin:
git fetch origin
git ls-remote --heads origin <BRANCH_NAME>
If branch not on origin:
- If FINAL REPORT was the source → STOP, workspace didn't push. Mark
push_missing, alert user. - If VK metadata was the source (FINAL REPORT missing) → flag
branch_mismatchand ask the user to inspect; do NOT silently try the truncated working branch name.
Record the verified branch into state.json[issue].branch so downstream skills
(vibe-status, vibe-merge) have a single canonical value.
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.
- 12d ago First seen · 248 lines · 41 tokens per session scan A 111b5a4629c2
vibe-link is a skill published in the GitHub repository OAI-Labs/vibe-flow (1 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,873 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
loop-on-ci
Monitor PR checks and fix failures until green. Uses gh pr checks as the source of truth for PR-attached checks.
pr-watch
Local PR watcher. Monitors CI status, automatically fixes failing checks by reading failure logs and applying targeted fixes, then optionally merges when all checks pass. Local CLI analog to Claude Code's cloud auto-fix feature.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
merge-review
Reviews pending fleet worktree merges before they're accepted. Reads the merge-check queue, detects file-level conflicts between branches, proposes a safe merge order, and surfaces reconciliation plans for overlapping changes.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
pr-feedback
Work a reviewer's comments on a pull request to the end - all three comment surfaces enumerated before any is triaged, every comment fixed, declined with a reason, or ticketed, push before you reply. Use when a PR comes back with review feedback or a red check.