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/SHAdd0WTAka/Zen-Ai-PentestWrote 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/shadd0wtaka/zen-ai-pentest/reality-checker)<a href="https://agentmods.dev/agents/shadd0wtaka/zen-ai-pentest/reality-checker"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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/shadd0wtaka/zen-ai-pentest/reality-checker"><img src="https://agentmods.dev/badge/agents/shadd0wtaka/zen-ai-pentest/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.00024 | $0.02048 |
| Opus 5.5 | $0.00010 | $0.00819 |
| Sonnet 5.5 | $0.00005 | $0.00410 |
| Haiku 4.5 | $0.00002 | $0.00205 |
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 1mo 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- Reality Checker — 95% identical, 5 lines differ
- reality-checker — 89% identical, 13 lines differ
- reality-checker — 84% identical, 28 lines differ
How it starts
The opening of the file, as written. The whole thing — 236 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.
- 1mo ago First seen · 236 lines · 24 tokens per session scan A 3c9459e83def
Reality Checker is an agent published in the GitHub repository SHAdd0WTAka/Zen-Ai-Pentest (499 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 2,048 once invoked, about $0.0001 per session on Opus 5.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-03.
Other agents, from other repositories
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
app-test-debug-agent
A testing and debugging assistant for web applications, using browser inspection, automated browser tests, local runs, and application logs.
checker
Fresh-context adversarial verification of completed work. Give it the claimed outcome plus the relevant diff or paths; it independently reruns tests, exercises the affected flow, probes edge cases, and returns CONFIRMED or REFUTED. Read-and-run only; it never plans, edits, or fixes anything.
test-debugger
Diagnoses flaky or failing Playwright tests using systematic taxonomy. Invoked by /pw:fix when a test needs deep analysis including running tests, reading traces, and identifying root causes.
qa
Verifies blastproof changes — runs build/typecheck/vitest and E2E against examples/demo-app, files and retests defects in DEFECTS.md. Use after dev implements tasks. Only qa may close a defect; never edits product code.