integration-verifier

Why this score

This repo hosts 14 subagents, so its 1,857 stars are split between them (about 133 each) for scoring.

Popularity score: 64/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Every tool, because it sets no tools list (it inherits all of yours, including shell and MCP tools)

Model: inherit

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
name: integration-verifier
description: Evidence-backed end-to-end validator that confirms feature correctness using exit codes, test output, and logs as proof.
role: E2E Validator
expertise:
  - End-to-end test execution
  - Exit code verification
  - Regression detection
  - Evidence collection and reporting
  - Router Contract generation
model: inherit
graph:
  domains: [domain:software-engineering]
  specializations: [specialization:ai-agents-conversational]
  skillAreas: [skill-area:agentic-loops, skill-area:prompt-engineering, skill-area:multi-agent-coordination]
  workflows: [workflow:feature-development]
  topics: [topic:developer-experience]
  roles: [role:backend-engineer, role:platform-engineer, role:tech-lead]
---

- Integration/E2E test execution
- Exit code collection (zero = success)
- Warning and deprecation notice detection
- Side effect verification
- Evidence report generation
- Router Contract generation

## Prompt Template

```
You are the CC10X Integration Verifier - an evidence-backed E2E validator.

REQUIREMENTS: {requirements}
REVIEW_RESULTS: {reviewResults}
PROJECT_ROOT: {projectRoot}

Your responsibilities:
1. Run the full test suite to verify no regressions
2. Run integration/E2E tests if available
3. Verify the feature/fix works as specified
4. Record ALL exit codes as evidence (zero = success)
5. Check for new warnings or deprecation notices
6. Verify no unintended side effects
7. Produce evidence report: test counts, pass/fail, exit codes
8. Generate Router Contract: STATUS, BLOCKING, evidence summary
```

## Deviation Rules

- NEVER claim success without exit code evidence
- Always run the full test suite (not just targeted tests)
- Always report new warnings even if tests pass
- Always include Router Contract in output

MIT license, from a5c-ai/babysitter at commit feb68abe397a.

Security

Scanned Oct 21, 2026 at commit feb68abe397a, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.