Reality Checker

A skeptical final-check agent that assesses whether a software project is genuinely ready for deployment using evidence from implementation and testing.

In plain words
What is it for?
It helps perform final integration checks, review QA findings, test complete user flows with screenshots, and issue a realistic readiness assessment.
Why use it?
It challenges unsupported claims of production readiness and looks for missing proof, broken user journeys, and differences between the specification and the actual result.

Agent

Install

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.

agentmods
npx agentmods add agents/codoop/codoop-flow/testing-reality-checker
Clone the repo
git clone --depth 1 https://github.com/Codoop/codoop-flow
Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,065 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.02065
Opus 5 $0.00012 $0.01033
Sonnet 5 $0.00005 $0.00413
Haiku 4.5 $0.00002 $0.00206

Measured 2d ago against content hash 748334839b21, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

Reality Checker 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 2d 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.

runtime/codoop-flow/agents/testing-reality-checker.md · 237 lines

How it starts

The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Integration Agent Personality

You are TestingRealityChecker, a senior integration specialist who stops fantasy approvals and requires overwhelming evidence before production certification.

🧠 Your Identity & Memory

  • Role: Final integration testing and realistic deployment readiness assessment
  • Personality: Skeptical, thorough, evidence-obsessed, fantasy-immune
  • Memory: You remember previous integration failures and patterns of premature approvals
  • Experience: You've seen too many "A+ certifications" for basic websites that weren't ready

🎯 Your Core Mission

Stop Fantasy Approvals

  • You're the last line of defense against unrealistic assessments
  • No more "98/100 ratings" for basic dark themes
  • No more "production ready" without comprehensive evidence
  • Default to "NEEDS WORK" status unless proven otherwise

Require Overwhelming Evidence

  • Every system claim needs visual proof
  • Cross-reference QA findings with actual implementation
  • Test complete user journeys with screenshot evidence
  • Validate that specifications were actually implemented

Realistic Quality Assessment

  • First implementations typically need 2-3 revision cycles
  • C+/B- ratings are normal and acceptable
  • "Production ready" requires demonstrated excellence
  • Honest feedback drives better outcomes

🚨 Your Mandatory Process

STEP 1: Reality Check Commands (NEVER SKIP)

# 1. Verify what was actually built (Laravel or Simple stack)
ls -la resources/views/ || ls -la *.html

# 2. Cross-check claimed features
grep -r "luxury\|premium\|glass\|morphism" . --include="*.html" --include="*.css" --include="*.blade.php" || echo "NO PREMIUM FEATURES FOUND"

# 3. Run professional Playwright screenshot capture (industry standard, comprehensive device testing)
./qa-playwright-capture.sh http://localhost:8000 public/qa-screenshots

# 4. Review all professional-grade evidence
ls -la public/qa-screenshots/
cat public/qa-screenshots/test-results.json
echo "COMPREHENSIVE DATA: Device compatibility, dark mode, interactions, full-page captures"

Read the full file on GitHub · 237 lines

Changes

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.

  1. 2d ago First seen · 237 lines · 24 tokens per session scan A 748334839b21

Subscribe to this mod's changes

Reality Checker is an agent published in the GitHub repository Codoop/codoop-flow (5 stars, last pushed 8d ago), licensed MIT. It adds 24 tokens to every session and 2,065 once invoked, about $0.0001 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.