Babysitter is a workflow engine for AI coding agents that enforces predefined steps, quality checks, human approvals, and decision records. It is used to coordinate complex, repeatable agent workflows across supported coding tools. The catalogue contains skills, agents, instructions, settings, a plugin, and an MCP integration for its workflow.
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 a5c-ai/babysitter --skill mcp-app-verificationgit clone --depth 1 https://github.com/a5c-ai/babysitterWrote 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/a5c-ai/babysitter/mcp-app-verification)<a href="https://agentmods.dev/skills/a5c-ai/babysitter/mcp-app-verification"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/mcp-app-verification/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/a5c-ai/babysitter/mcp-app-verification"><img src="https://agentmods.dev/badge/skills/a5c-ai/babysitter/mcp-app-verification.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.00048 | $0.03084 |
| Opus 5 | $0.00024 | $0.01542 |
| Sonnet 5 | $0.00010 | $0.00617 |
| Haiku 4.5 | $0.00005 | $0.00308 |
Grade A, and why
mcp-app-verification 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 5d 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 — 348 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-app-verification
Run comprehensive verification checklists for MCP Apps covering correctness, compatibility, and migration completeness.
Overview
MCP Apps have several critical invariants that must be verified before deployment. This skill provides systematic verification across multiple dimensions:
- Runtime verification: App loads and functions in basic-host reference
- Pattern verification: Critical code patterns are correct (handler-before-connect, text fallback)
- Build verification: Single-file bundle is valid and complete
- Styling verification: Host theming applies correctly
- CSP verification: All origins declared, no silent failures
- Migration verification: No remaining legacy patterns (OpenAI, old MIME types, snake_case)
Capabilities
basic-host Test Execution
- Build the MCP App
- Start the server
- Launch basic-host reference implementation against the server
- Verify app loads without console errors
- Verify handlers fire correctly
Handler-Before-Connect Invariant
- Search source code for
app.connect()call - Verify ALL handlers (
ontoolinput,ontoolresult,onhostcontextchanged,onteardown) are registered BEFORE connect - Flag violations -- handlers registered after connect will silently not work
Text Fallback Verification
- Search all tool handlers for
contentarray in return value - Verify each tool returns at least one
{ type: 'text', text: '...' }entry - Flag tools that only return
structuredContentwithout text fallback
Resource URI Link Integrity
- Extract all
resourceUrivalues fromregisterAppToolcalls - Extract all URIs from
registerAppResourcecalls - Verify every tool
resourceUrihas a matching registered resource - Flag orphaned resources (registered but not referenced)
Single-File Bundle Verification
- Build the project
- Verify
dist/mcp-app.html(or equivalent) exists - Check the HTML file is self-contained (no external
<script src>,<link href>,<img src>to relative paths) - Verify
vite-plugin-singlefileis in dev dependencies
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.
- 5d ago First seen · 348 lines · 48 tokens per session scan A 6567b98e4079
mcp-app-verification is a skill published in the GitHub repository a5c-ai/babysitter (1,783 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 3,084 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
goga-accept-test-assessment
Cell test coverage assessment for acceptance review.
goga-accept-usage-review
Validate cell-level usage files against actual implementation during acceptance.
goga-accept-scope
Defines the acceptance scope — the set of cells for a given functionality.
goga-change-test-engineer
Test Coverage Validation and Behavioral Testing.
rn-testing
This skill should be used when the user asks to "write a Maestro test", "create E2E flows", "add testIDs", "run UI tests", "run E2E tests", "verify a feature works", "test my screen", "set up maestro-runner", "mock network requests", "inspect store state", "write test assertions", or needs guidance on test timing…
capturing-proof
This skill should be used when the user asks to "capture proof", "record a demo of this feature", "make a video showing it works", "record the flow for the PR", "generate a PR body", "capture screenshots for the PR", "proof-capture", or when a verified feature needs PR-ready proof artifacts (video + numbered…