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 ivy00johns/Skill-Madness --skill babysitgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/babysit)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/babysit"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/babysit/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/ivy00johns/skill-madness/babysit"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/babysit.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.00233 | $0.02497 |
| Opus 5 | $0.00117 | $0.01248 |
| Sonnet 5 | $0.00047 | $0.00499 |
| Haiku 4.5 | $0.00023 | $0.00250 |
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 9d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
babysit
A configuration of [
loop-controller]. That skill supplies the loop machinery — primitive selection, the full guardrail stack, state externalization. This skill supplies the three things specific to "keep a PR healthy": the per-pass recipe (it schedules [git-pr-feedback], it does not re-implement it), the mechanical proof (zero open blocking findings + mergeable), and the HITL boundary that decides what's AFK-safe vs what pauses. Readloop-controllerfor the guardrails; they're inherited, not repeated here.Why
disable-model-invocation: this loop commits, pushes, rebases, and touches a live PR thread on its own, on a clock. It is user-driven — you want to type/loop 5m /babysit(or/babysit), not have Claude silently start tending a PR because a reviewer happened to comment.
The 5-part contract
| Part | This loop |
|---|---|
| trigger | an open PR of yours with potential review activity; scheduled via /loop 5m /babysit, or an explicit /babysit (optionally a PR number) |
| action | ONE pass: fetch new review findings (Copilot + human) via [git-pr-feedback] → triage → address one root-cause finding (or rebase if base moved) → re-run the project gate → push → reconcile the PR thread. One change per pass; re-check the whole PR state after |
| proof | the gh PR review/status query returns zero OPEN actionable/blocking comments AND mergeable == "MERGEABLE" (up to date with base, CI green) — default-FAIL: assume findings are unaddressed until the fetch proves otherwise (treat mergeable == "UNKNOWN" as not-yet-proven and re-check) |
| memory | a per-PR fix log (findings addressed, findings deferred + why), git history, and the PR thread itself — all durable across the session-scoped /loop fires |
| stop | zero blocking findings AND mergeable OR poll/iteration cap OR no-progress for 3 rounds (same finding unaddressed 3×) OR budget cap OR an HITL checkpoint is hit |
What ships with it
1 file 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.
- 9d ago First seen · 176 lines · 233 tokens per session scan A e67cfc6b7dd8
babysit is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed today), licensed MIT. It adds 233 tokens to every session and 2,497 once invoked, about $0.0012 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-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…
write-pr
Reference standards for writing pull request titles and descriptions in the tldraw repository, plus the pre-flight comment sweep over the diff. Use as supporting guidance when another skill or workflow needs PR content standards, not as the user-facing create/update PR workflow.