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 charlesjones-dev/claude-code-plugins-dev --skill workflow-babysitgit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/workflow-babysit)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/workflow-babysit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-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/charlesjones-dev/claude-code-plugins-dev/workflow-babysit"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/workflow-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.00127 | $0.03850 |
| Opus 5.5 | $0.00051 | $0.01540 |
| Sonnet 5.5 | $0.00025 | $0.00770 |
| Haiku 4.5 | $0.00013 | $0.00385 |
Grade A, and why
workflow-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 14d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/workflow-babysit - Babysit a change to production
Run the whole release path for the current branch without stopping for approval at each hop. Invoking this skill, by slash command or by asking to babysit a change to production, is the approval to commit, open PRs, reply on review threads, merge and promote to production.
Assume the user has walked away. Ask every question in step 0, before any waiting starts. After that, only stop for the cases under "When to stop".
User provided: $ARGUMENTS
The arguments may name a PR number to babysit instead of the current branch's PR, and may say what to do once the change is live.
Repo settings
Read the project's CLAUDE.md and the user's ~/.claude/CLAUDE.md first. When they say anything about how this repo reviews, merges or deploys, it wins over the defaults in this skill. Look for:
- Review triage: what to fix before merging and what to defer. Replaces the default triage bar in reviewers.md.
- What to do when Claude Code review is off: use the local review, proceed without it, or stop. Answers the step 0 question ahead of time.
- Deploy: the host, which services to watch, health-check URLs for production and staging, and anything that must happen before or after a deploy (for example, starting a staging database before merging into staging, or tearing staging down afterwards).
- Merge method for feature PRs.
0. Set up (once per run, all questions here)
Collect everything below, then ask all the questions it raises in one AskUserQuestion call.
- Repo:
gh repo view --json nameWithOwner,defaultBranchRef,mergeCommitAllowed,squashMergeAllowed,rebaseMergeAllowed,deleteBranchOnMerge,git branch --show-current,git status --short. - Where this run starts:
- If the arguments name a PR, or the branch has an open PR, read its
baseRefName. - If you're on the staging branch with nothing uncommitted, no local commits ahead of
origin/staging, and staging ahead of the default branch, this is a resumed run: go straight to step 5 after step 0. - Otherwise a new PR will be opened in step 1.
- If the arguments name a PR, or the branch has an open PR, read its
- Branch flow: the repo has a staging flow if a
staging(ordevelop) branch exists on origin and recent PRs into the default branch come from it (gh pr list --state merged --base <default> --limit 5 --json headRefName). An existing PR's own base decides what happens to it: a PR into staging goes through steps 4 and 5, and a PR straight into the default branch skips them. A new PR targets staging when the repo has a staging flow, and the default branch otherwise. - Merge method: for feature PRs, CLAUDE.md first, then what recent merged PRs used, then whichever single method the repo allows. Release PRs from staging use a merge commit so staging and the default branch don't diverge. If the repo doesn't allow merge commits, use the method past release PRs used.
- Uncommitted changes: list them. They'll be committed into the PR in step 1. If some look unrelated to the change (scratch files, logs, local config, work in progress elsewhere), ask which to leave out.
- Unreleased staging work (staging flow only): list the commits staging would promote, with their GitHub logins:
What ships with it
2 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.
- 14d ago First seen · 169 lines · 127 tokens per session scan A 8ac0333e914a
workflow-babysit is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (35 stars, last pushed 14d ago), licensed MIT. It adds 127 tokens to every session and 3,850 once invoked, about $0.0005 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-10-11.
Other skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.