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 agentmods add skills/wibias/github-delivery/babysitnpx skills add Wibias/github-delivery --skill babysitgit clone --depth 1 https://github.com/Wibias/github-deliveryWhat 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 | $0.00098 | $0.00440 |
| Opus 5 | $0.00049 | $0.00220 |
| Sonnet 5 | $0.00020 | $0.00088 |
| Haiku 4.5 | $0.00010 | $0.00044 |
Grade A, and why
babysit 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.
What it actually says
Babysit → github-delivery
Cursor’s built-in babysit (~/.cursor/skills-cursor/babysit) is a thin
conflict/CI stub. It reinstalls when deleted. Do not follow it when this
personal skill or github-delivery is available.
Do this instead
-
Load skill
github-delivery(usually~/.agents/skills/github-deliveryor~/.cursor/skills/github-delivery). -
Load
github-deliverySKILL.mdand the matching workflow (policy modules are declared in the workflow):- Default for babysit/watch/monitor →
references/watch-pr.md - If they asked merge-ready →
references/fix-pr-bots.md
- Default for babysit/watch/monitor →
-
First command every wake (watch):
node "<github-delivery>/scripts/watch-wake-gate.mjs" OWNER/REPO NExit
1→ triage OWNER/MEMBER comments in code (rebase/drop overlap / keep leftovers); resolve DIRTY conflicts. ACK-only does not clear. Never report waiting on CI/CodeRabbit while exit1. -
Ordering: reviews/owners → tip update → CI. Never merge-
dev-then-idle.
Do not
- Follow only the built-in babysit steps (conflicts / CI / Bugbot stub).
- Say “up to date with dev; waiting on windows-latest and CodeRabbit” while wake-gate fails.
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 First seen · 36 lines · 98 tokens per session scan A 79f26e3ddb98
babysit is a skill published in the GitHub repository Wibias/github-delivery (5 stars, last pushed 2d ago), licensed MIT. It adds 98 tokens to every session and 440 once invoked, about $0.0005 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.