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.
git clone --depth 1 https://github.com/Vibiz-ai/vibiz-claude-pluginWrote 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/commands/vibiz-ai/vibiz-claude-plugin/daily-digest)<a href="https://agentmods.dev/commands/vibiz-ai/vibiz-claude-plugin/daily-digest"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/daily-digest/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/commands/vibiz-ai/vibiz-claude-plugin/daily-digest"><img src="https://agentmods.dev/badge/commands/vibiz-ai/vibiz-claude-plugin/daily-digest.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.00035 | $0.01170 |
| Opus 5 | $0.00017 | $0.00585 |
| Sonnet 5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
daily-digest 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 11d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/vibiz:daily-digest
One-time setup for a daily autonomous digest of every brand under the user's Vibiz workspace group. Once scheduled, it fires every morning, calls the Vibiz MCP for inbox + analytics, and emails / messages the result.
Why this exists
Manual checks don't happen. People install Vibiz, generate a few ads, and forget to look at inbox replies, comment moderation, or which posts performed. A scheduled routine fixes that — the digest comes to them.
Steps
-
MCP gate. Try
list_vibiz. If unauthed → tell user/mcp→ vibiz → Authenticate → re-run. Stop. Otherwise note the brand count and ask:I'll set up a daily Vibiz digest for your <N> brand(s). Each morning at 9am local you'll get: - New inbox conversations + comments needing replies - Top-performing posts in the last 24h - Best post time per brand - Daily metrics deltas Delivery: where would you like it? (1) email — paste address, (2) the Vibiz agent chat, (3) both. Default: both. What time should it fire? (default: 09:00 your local TZ) -
Compose the routine prompt. Build a self-contained prompt the scheduled agent will run. The prompt MUST be deterministic — same wording every day, no live state assumed. Template:
Daily Vibiz digest. For each brand returned by `list_vibiz`: 1. Call `vibiz_inbox_conversations({ target: { vibiz: <slug> }, limit: 20 })` — list new DMs unread in last 24h. 2. Call `vibiz_inbox_comments({ target: { vibiz: <slug> }, limit: 20 })` — surface comments needing reply. 3. Call `vibiz_analytics_top_posts({ target: { vibiz: <slug> }, period: "1d" })` — top-performing posts last 24h. 4. Call `vibiz_analytics_best_time({ target: { vibiz: <slug> } })` — recommended post time today. 5. Call `vibiz_analytics_daily_metrics({ target: { vibiz: <slug> } })` — yesterday vs today delta. Format as a single concise digest grouped by brand. Lead with anything that needs human action (unread DM, unanswered comment, anomaly in metrics). Follow with the wins (top post, best time tomorrow). <DELIVERY_INSTRUCTION>
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.
- 11d ago First seen · 82 lines · 35 tokens per session scan A a5a53a087bfd
daily-digest is a command published in the GitHub repository Vibiz-ai/vibiz-claude-plugin (7 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 1,170 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.