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 avibe-bot/avibe --skill background-watch-hookgit clone --depth 1 https://github.com/avibe-bot/avibeWrote 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/avibe-bot/avibe/background-watch-hook)<a href="https://agentmods.dev/skills/avibe-bot/avibe/background-watch-hook"><img src="https://agentmods.dev/badge/skills/avibe-bot/avibe/background-watch-hook/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/avibe-bot/avibe/background-watch-hook"><img src="https://agentmods.dev/badge/skills/avibe-bot/avibe/background-watch-hook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 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 Tool Misuse · line 333 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
- medium Tool Misuse · line 438 Tool defaults are unsafe or overly permissive (e.g. disabled TLS verification, no authentication, world-writable permissions). Unsafe defaults widen the attack surface.Fix: Override unsafe defaults with secure settings (verify=True, auth required, restrictive permissions). Review and harden all tool configurations.
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.00032 | $0.01336 |
| Opus 5.5 | $0.00013 | $0.00534 |
| Sonnet 5.5 | $0.00006 | $0.00267 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
background-watch-hook 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 2d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Background Watch Hook
Use vibe watch for a durable wait that resumes an Agent when an external event
arrives. The waiter detects events; the follow-up Agent verifies live state and
acts. A success candidate is not merge authorization.
Contract and lifecycle
| Waiter exit | Meaning |
|---|---|
0 |
One new reportable event; summary on stdout |
75 (or configured retry code) |
Still waiting; no Agent turn |
64 plus avibe-watch: no-event on stderr |
Quiet completed cycle: retire once, re-arm forever |
124 or other terminal failure |
Notify the Agent and stop |
A bare 64 is an error. Keep diagnostics on stderr. A once Watch waiting for its
first event uses a retry code, not 64. Forever waiters need durable cursors or
edge detection; a persistent true condition is not a new event. Avibe serializes
follow-ups, re-arms after they settle, and pauses rapid repeated events for repair.
- Read
vibe watch add --helpbefore first use; inspect/update withvibe watch <list|show|update|pause|resume|remove>. --timeoutbounds each cycle (default six hours);--lifetime-timeoutbounds the whole Watch. Use0for an intentionally unbounded PR delivery loop.- Remove the Watch at close-out. Do not use detached shells for durable waits.
Session targeting
- Inside an Avibe-injected Agent shell, omitting the target continues this conversation.
- Use
--session-id <id>only when resuming a different existing Agent Session. - Use
--create-session --same-scopefor one visible sibling Session; use--create-session-per-run --same-scopefor a separate visible Session per event. - Use
--scope-id <scopes.id>instead of--same-scopefor an explicit scope. - If
--cwdis omitted, Avibe uses the command's current working directory.
Preferred PR + CI watch
Use --forever and one owner-specific state file for the whole loop. Seed and
arm before the watched push/review trigger; for a new PR, create it first, then
immediately seed/arm. Keep the same Watch and cursor across all later rounds.
What ships with it
6 files 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.
- 2d ago Changed · +4 lines d896d7bddde9
- 5d ago Changed 9f1bbcbc1b49
- 10d ago Changed · -460 lines · -12 tokens per session 8de17d5568ab
- 1mo ago Changed · +17 lines 59507a4ebbec
- 1mo ago First seen · 544 lines · 44 tokens per session scan A d848dc785df0
background-watch-hook is a skill published in the GitHub repository avibe-bot/avibe (632 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,336 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
git-expert
Git operations expert for branching, rebasing, conflicts, and workflows.
github
GitHub operations expert for PRs, issues, code review, Actions, and gh CLI.
nano-banana-pro-openrouter
Deterministic OpenRouter image generation adapter for Nano Banana Pro / Gemini image models. Use as skillexec when a meta-skill needs local image files and structured IMAGEREADY records without spawning an LLM agent.
skill-creator-linter
Internal tool (not user-invocable). Called by meta-skill-creator as a DAG step (kind: agent) to lint a candidate meta-skill SKILL.md against G1 (parse + reference check + xmlescape grep + structural lint) and G2 (scheduler dry-run with stub executors). Deterministic, sub-second, no LLM. Returns JSON diagnostics.
paper-abstract-author
Write the abstract after the paper body has been revised, using the final claims and evidence.
clinicaltrials-database
Query ClinicalTrials.gov via API v2. Search trials by condition, drug, location, status, or phase. Retrieve trial details by NCT ID, export data, for clinical research and patient matching.