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-standupgit 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-standup)<a href="https://agentmods.dev/skills/oai-labs/vibe-flow/vibe-standup"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-standup/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-standup"><img src="https://agentmods.dev/badge/skills/oai-labs/vibe-flow/vibe-standup.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.01239 |
| Opus 5 | $0.00020 | $0.00620 |
| Sonnet 5 | $0.00008 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
vibe-standup 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.
curl -X POST -H 'Content-Type: application/json' \ How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibe-standup
Overview
Compose a human-readable summary of vibe-flow activity for Slack, Discord, or team update channels. Auto-detects the relevant time window.
Core principle: Crisp, copy-pasteable, links everywhere.
Announce at start: "I'm using the vibe-standup skill to compose a summary."
When to use
- User asks for "daily report", "standup", "summary", "what got done"
- End of
vibe-shiprun (auto-invoked) - Scheduled via
/loopor cron for recurring updates
The process
Step 1: Determine time window
Default: last 24 hours. User can override:
today→ since midnight localthis-week→ since Mondayrun→ this vibe-ship run (from state.json start timestamp)--since YYYY-MM-DD→ arbitrary
Step 2: Gather data
- Load
state.json(and any rotatedstate.json.<run-id>archives in window) - For each issue touched in window:
- status transitions (dispatched → merged, etc.)
- PR URL, commit SHA
- Agent cost estimate
- Query MCP
list_issuesfiltered byupdated_atfor additional context - Query GitHub for PRs merged in window:
gh search prs --merged="<window>" --author="@me"
Step 3: Categorize
Bucket each issue into ONE of:
- Merged (done in window)
- In review (PR open, awaiting review or with review in progress)
- In progress (workspace running)
- Blocked (human intervention needed)
- Abandoned (dropped in window)
Step 4: Compose summary
Format (Markdown, Slack/Discord-compatible):
# vibe-flow standup — <YYYY-MM-DD>
**Window:** last 24h | **Project:** a20k-project
## ✅ Merged (3)
- [A20K-1] Remove AI Literacy column — [#42](https://github.com/.../42) — T0 flash — 2m
- [A20K-3] Add pagination to dashboard — [#43](https://github.com/.../43) — T2 sonnet-hi — 18m
- [A20K-4] Refactor login form — [#45](https://github.com/.../45) — T1 sonnet-med — 9m (escalated T1→T2)
## 🔍 In review (2)
- [A20K-5] Auth OIDC migration — [#44](https://github.com/.../44) — T2 — review by @reviewer pending
- [A20K-6] Form validation — [#46](https://github.com/.../46) — T1 — CI running
## 🏗️ In progress (1)
- [A20K-8] Wire notifications — T3 opus — workspace started 15m ago
## 🛑 Blocked (1)
- [A20K-7] Data migration — escalation limit hit (3 fix attempts). Needs human.
## 📊 Metrics
- **Cost (window):** ~$3.77
- **Merged LoC:** +412 / -89
- **Avg wall-time per merged issue:** 12m
- **Escalation rate:** 1/4 (25%)
## 🎯 Wave status
Wave 1 barrier: 2/4 merged. Waiting on A20K-5 (in review), A20K-7 (blocked).
## Next actions
- Review A20K-5 PR
- Unblock A20K-7 — design call needed
- Wave 2 will unblock once Wave 1 closes
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 · 141 lines · 41 tokens per session scan A 1d4e34f4a761
vibe-standup 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,239 once invoked, about $0.0002 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-31.
Other skills, from other repositories
lead
Use when acting as the factory tech lead: classify work, ask the minimum questions, create tickets, and dispatch without implementing.
to-tickets
Use when breaking a plan into tracer-bullet GitHub issues with blocking edges.
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.
workspace
Multi-repo campaign coordinator. Same lifecycle as fleet -- scope claims, discovery relay, wave-based execution -- but the unit of work is a repo, not a file. Coordinates campaigns across repositories with shared context.
decision-map
Turn a loose idea into a git-tracked, session-resumable map of typed investigation tickets, then drive them to resolution one at a time. The planning-loop engine for work that is still being figured out — too fuzzy for a campaign, too big for a single intake item. Resolved tickets graduate into .planning/intake/ for…
unharness
Safely leave Citadel using the active adoption receipt. Produces a no-write, reviewable plan, preserves a portable archive, removes only exact owned material, and reports modified or externally registered surfaces as retained or unknown. Legacy installs must be imported before exact leave is claimed.