# Agent Output Verifier

> Use when agent-produced work needs a safety, evidence, and reliability check before handoff, merge, or trust.

- Skill: `rohitg00/agent-output-verifier` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rohitg00/agent-output-verifier`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rohitg00/agent-output-verifier/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: rohitg00 (https://skillmd.com/u/rohitg00)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rohitg00/agent-output-verifier

---


# agent-output-verifier

Lifecycle stage: REVIEW

## Trigger

Use before trusting or handing off output produced by an autonomous or semi-autonomous agent, especially after long-running work, tool use, code generation, external calls, or multi-step planning.

Do not use as a replacement for domain review. This skill decides whether the output is safe and evidenced enough to enter the next review gate.

## When not to use
Do not use when this trigger is absent; choose the command or skill that owns the requested state, artifact, and verification gate.

## Inputs

- Agent output or artifact.
- Original user request and constraints.
- Tool logs, test logs, diffs, screenshots, traces, or citations.
- List of tools the agent claimed to use.
- Allowed scope, files, commands, and side effects.
- Known secrets, private paths, or data classes that must not appear.

## Procedure

1. Restate the claimed outcome in one sentence.
2. Check for secret leakage: credentials, tokens, private URLs, keys, personal data, or connection strings.
3. Check for hallucinated tools or evidence: claimed commands, tests, APIs, files, screenshots, or links that have no supporting proof.
4. Check for unbounded loops: retry loops, background jobs, recursive scheduling, polling, or autonomous goals without stop conditions.
5. Check for skipped gates: tests not run, validation missing, review bypassed, user approval omitted, or destructive actions performed silently.
6. Check scope control: files changed, external calls made, and side effects match the request.
7. Classify the output as `pass`, `pass-with-warnings`, or `blocked`.
8. Produce a blocker list with exact evidence needed to unblock.

## Anti-Rationalization

| Shortcut | Rebuttal |
|---|---|
| "The output sounds careful." | Fluency is not evidence; require logs, diffs, citations, approvals, or traces. |
| "The agent said tests passed." | Test claims need current command output or an explicit missing-evidence blocker. |
| "Only small side effects happened." | Any side effect must match the allowed scope and approval evidence. |

## Verification

- Every pass/fail statement points to evidence or says evidence is missing.
- Secrets and private data are either absent or redacted.
- Claimed tools and tests have inspectable logs or artifacts.
- Loops have measurable stop conditions.
- Side effects match the allowed scope.
- The final status is one of `pass`, `pass-with-warnings`, or `blocked`.

## Output Artifact

Produce a verifier decision with status, checked claims, evidence references, blockers, warnings, required approvals, and the smallest safe next action.

## Failure Modes

- Approving fluent but unverifiable output.
- Treating screenshots, logs, or test names as proof without checking content.
- Ignoring hidden side effects because the final summary sounds successful.
- Missing recursive automation or infinite retry behavior.
- Leaving secrets in the verification report.
- Expanding into a full code review when the needed decision is trust/block.

## Example

Trigger: agent-produced output must be trusted, blocked, or routed for repair. Action: check evidence, secrets, invented tools, skipped tests, unsafe side effects, and loop limits before handoff. Output artifact: `templates/review-report.md` with blockers and next action. Verification: cite each pass, blocker, artifact path, and validation proof.

```markdown
Status: blocked

Claim checked: "All tests pass and deployment is ready."

Blockers:
- No test log or command output attached for the claimed passing tests.
- Deployment step is outside the allowed scope.
- Background retry worker has no stop condition.

Evidence needed to unblock:
- Test command and output.
- Scope approval for deployment.
- Retry limit or cancellation rule.
```