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 roedyrustam/vibes-plug --skill proactive-background-watchergit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/proactive-background-watcher)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/proactive-background-watcher"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/proactive-background-watcher/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/roedyrustam/vibes-plug/proactive-background-watcher"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/proactive-background-watcher.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.00046 | $0.01891 |
| Opus 5.5 | $0.00018 | $0.00756 |
| Sonnet 5.5 | $0.00009 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
proactive-background-watcher 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Proactive Background Watcher (Sentinel Daemon Protocol)
English
Orchestration & Integration
- Upstream & Task Lifecycle:
zero-to-prod-orchestrator(Phase 7-8 lifecycle),session-memory-manager(checkpoint sentinel state),brainstorming. - Background Cron & Execution:
cron-scheduler-expert(app-level cron vs agent-native schedule tool),parallel-tool-orchestrator(concurrent polling jobs). - Incident Escalation & Self-Healing:
self-healing-cloud-orchestrator(auto-patch upon anomaly detection),logging-error-tracking-expert(Sentry/Pino trace alerts). - Build & CI/CD Watchers:
ci-cd-devops-architect(pipeline completion checks),cloud-hosting-expert(Vercel/Railway build state).
Description
Standard LLM chat sessions are strictly reactive—they remain dormant until the user submits a prompt. This skill unlocks proactive agency. Utilizing the runtime's native schedule tool (one-shot timers and recurring cron schedules), the agent can autonomously monitor background build pipelines, poll health endpoints, inspect server logs, or track deployment state machines. When an anomaly occurs or a long-running job finishes, the agent wakes up autonomously to diagnose, notify, or remediate without waiting for human prompting.
Trigger Conditions
- User requests asynchronous monitoring: "Let me know when the Vercel build succeeds", "Watch the test runner", or "Alert me if memory spikes".
- Running long-running database migrations or load tests in the background.
- Scheduled recurring health audits (e.g., periodic SSL expiry or API latency checks).
- Watchdog supervision over multi-agent swarm subtasks.
Sentinel Execution Architecture
User Prompt: "Run migrations and alert me when complete"
│
▼
1. Launch Background Task (run_command with WaitMsBeforeAsync=500)
│
▼
2. Register Sentinel Timer via `schedule`
(DurationSeconds=120, Prompt="Check migration task status", TimerCondition="task-id")
│
▼
3. Agent Ends Turn (System enters reactive sleep state)
│
▼
4. Autonomous Wakeup on Timer Expiration or Task Completion
│
├─► Success ──► Synthesize artifact & notify user
└─► Error ──► Trigger `autonomous-tdd-debugger` or `self-healing-cloud-orchestrator`
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 cb9ef338d7e8
- 3d ago Changed · +1 lines cd0b85042aa5
- 6d ago Changed · +77 lines 822c01be3d69
- 15d ago Changed 9bb343507b9d
- 20d ago Changed 912eb3f0da81
- 21d ago Changed 7966c22093d1
- 23d ago Changed · -6 lines · +34 tokens per session d053793e5cf1
- 25d ago Changed · +6 lines · -34 tokens per session d366c5e3e2b6
- 1mo ago Changed c1c737d40605
- 1mo ago First seen · 69 lines · 46 tokens per session scan A f00648e7bbc3
proactive-background-watcher is a skill published in the GitHub repository roedyrustam/vibes-plug (113 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 1,891 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
routine-contract
The operating contract for any scheduled or unattended agent session — a cron job, a Routine, a CI-triggered agent, a nightly sweep. Use when writing, reviewing, debugging or scheduling automation that runs without a human present, and whenever a scheduled job reports success but you cannot find what it produced.…
bash
Expert Bash shell scripting assistance covering POSIX compliance, parameter expansion, pipelines, traps, and debugging. Use when writing robust shell scripts, automating DevOps tasks, or handling file processing.
turborepo
Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines…
token-saver
Token optimization guide for Claude Code. This skill should be used when the user wants to reduce API costs, learn model routing strategies, or understand how to use free/cheaper tools (Ollama, Haiku) instead of burning expensive Claude tokens on routine tasks. Triggers on: save tokens, reduce costs, token tips, cheap…
ci-cd-and-automation
Automates CI/CD pipeline setup. Use when setting up or modifying build and deployment pipelines. Use when you need to automate quality gates, configure test runners in CI, or establish deployment strategies.
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.