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 divingsbysangam/salesforce-compound-engineering-plugin --skill sf-babysit-prgit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWrote 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/divingsbysangam/salesforce-compound-engineering-plugin/sf-babysit-pr)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-babysit-pr"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-babysit-pr/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/divingsbysangam/salesforce-compound-engineering-plugin/sf-babysit-pr"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-babysit-pr.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.00107 | $0.01703 |
| Opus 5 | $0.00053 | $0.00851 |
| Sonnet 5 | $0.00021 | $0.00341 |
| Haiku 4.5 | $0.00011 | $0.00170 |
Grade A, and why
sf-babysit-pr 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 10d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Babysit a PR
Keep an open PR continuously moving toward merge by reacting to three independent event streams — incoming review comments, CI status changes, and branch currency — as each arrives, for as long as the PR stays open. Comment fixes are delegated to sf-resolve-pr-feedback; CI failures are delegated to sf-debug; routine target-local base movement follows the bounded protocol below. This skill owns the watch loop: snapshot, order, dedup, act, and decide when to keep watching, move to the next authorized managed-stack layer, or stop.
Outcome: leave the requested PR at an honest terminal, looks-ready, blocked, or budget state. For an independent PR or manual dependency chain, that target-local result is done. For a confirmed managed stack, a settled requested layer is a transition checkpoint: offer stack-wide continuation once when another immediate non-draft layer needs work; if accepted, babysit one layer at a time and stop advancement at the first draft not explicitly in scope, a human-blocked layer, the end of the stack, or the normal budget/user stop. Never infer this broader semantic scope from branch topology alone. Done: a Step 3 true stop reached and a Step 4 report written. Settled ≠ merged.
Required reads (procedure lives here, not in this file): references/envelope.md (mutation envelope, looks-ready signals, asking/invoking), references/setup.md (Step 1), references/tick.md (Step 2), references/settle.md (Step 3), references/report.md (Steps 4–5), references/watch-loop.md (scheduling, state, dedup).
Non-negotiable boundaries
- Merge-readiness is never merge authorization. This skill never merges as part of babysitting; only a separate explicit user request to merge can authorize that action.
- Draft PRs are opt-in. Never review or babysit a draft merely because managed-stack traversal reaches it.
- Managed means positively confirmed membership. Fresh probe must emit
manager_status == "confirmed". - One semantic writer lane. Keep one active PR target and one watcher.
What ships with it
7 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.
- 10d ago First seen · 63 lines · 107 tokens per session scan A 211ceb6098df
sf-babysit-pr is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 6d ago), licensed MIT. It adds 107 tokens to every session and 1,703 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
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.