real-data-auditor

Scan TypeScript/Next.js repositories for mock data and unvalidated API responses.

4|1|Updated Feb 12, 2026
One-click install
npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill real-data-auditor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: real-data-auditor
Source: https://github.com/0xjc65eth/CYPHER-V3/tree/main/skills/real-data-auditor
Command: npx skills add https://github.com/0xjc65eth/CYPHER-V3 --skill real-data-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Real Data Auditor enforces a zero-tolerance policy for simulated, hardcoded, or placeholder data in CYPHER V3 by scanning source files and API routes to ensure every visible number originates from a verified external source.

Core Features & Use Cases

  • Multi-layer scanning: Searches for explicit mock flags, conditional mock toggles, Math.random misuse, hardcoded arrays, placeholder strings/numbers, and API responses returned without schema validation.
  • API validation mapping: Recommends real upstream endpoints and cache TTLs for common data sources (e.g., CoinGecko, Hiro, UniSat, Mempool, Ordiscan) and maps mock replacements to their real counterparts.
  • Audit reporting: Produces a scored, timestamped audit with file-level findings, remediation guidance, and a summary of confirmed live data.
  • Use Case: Run pre-release to validate that market prices, token data, and fee estimates are live, validated, and not generated by mocks or placeholders.

Quick Start

Run the Real Data Auditor to scan the repository for mock patterns, Math.random misuse, hardcoded arrays, and unvalidated API responses and generate an actionable audit report.

Frequently Asked Questions about real-data-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect mock data and hardcoded arrays in a TypeScript codebase?

To detect mock data in a TypeScript codebase, scan source files and API routes for explicit mock flags, Math.random misuse, hardcoded arrays, and placeholder values using pattern-based heuristics.

How do I validate API responses using Zod schema validation in Next.js?

Validating API responses using Zod involves checking if schema-validation detection is applied to unvalidated API routes. The auditor flags API responses returned without schema validation and recommends implementing Zod schemas.

What's the best way to eliminate placeholder values from production API routes?

The best way to eliminate placeholder values from production API routes is to run a pre-release audit that maps mock replacements to real upstream endpoints, enforcing a zero-tolerance policy for simulated data.

Can I automate data integrity audits for live market prices and token data?

Yes, you can automate data integrity audits for live market prices and token data by scanning repositories for unvalidated API responses and generating a scored, timestamped audit report with remediation guidance.

Does the real data auditor recommend specific API endpoints and cache TTLs?

The real data auditor recommends real upstream endpoints and cache TTLs for common data sources like CoinGecko, Hiro, UniSat, Mempool, and Ordiscan, mapping mock replacements to their live counterparts.

Why does my Next.js repository still show hardcoded numbers after an audit?

Hardcoded numbers may remain after an audit if they are missed by pattern-based heuristics or overlooked as placeholder strings. Running a multi-layer scan ensures confirmed live data replaces all simulated values.