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.
git clone --depth 1 https://github.com/timurgaleev/vibestackWrote 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/agents/timurgaleev/vibestack/reality-checker)<a href="https://agentmods.dev/agents/timurgaleev/vibestack/reality-checker"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/reality-checker/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/agents/timurgaleev/vibestack/reality-checker"><img src="https://agentmods.dev/badge/agents/timurgaleev/vibestack/reality-checker.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.00039 | $0.02113 |
| Opus 5.5 | $0.00016 | $0.00845 |
| Sonnet 5.5 | $0.00008 | $0.00423 |
| Haiku 4.5 | $0.00004 | $0.00211 |
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 19d 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.
This is a copy
89% identical to Reality Checker — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 241 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"
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.
- 19d ago First seen · 241 lines · 39 tokens per session scan A 80421bc31f23
reality-checker is an agent published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 7d ago), licensed MIT. It adds 39 tokens to every session and 2,113 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to Reality Checker, differing in 13 lines, and is treated as a copy.
Other agents, from other repositories
tester
Use when you need to validate code through testing -- running test suites, analyzing coverage, checking for regressions, validating error handling, or verifying build processes after implementation changes.
e2e-runner
End-to-end testing specialist using Vercel Agent Browser (preferred) with Playwright fallback. Use PROACTIVELY for generating, maintaining, and running E2E tests. Manages test journeys, quarantines flaky tests, uploads artifacts (screenshots, videos, traces), and ensures critical user flows work.
ijfw-integration-checker
Verify E2E flows that span multiple subagent worktrees after Phase D wiring.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
qa-executor
Executes QA test plans with detailed reporting. Specialized for API testing and event verification.
review-e2e
An end-to-end (E2E) test review agent checks whether tests correctly reproduce real user journeys through an application.