[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M797B6GD5RH0S0SD9TFM2Y27":3,"skill-same:01M797B6GD5RH0S0SD9TFM2Y27":64},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":14,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":49,"install":50,"resources":63},"01M797B6GD5RH0S0SD9TFM2Y27","mock-hunter",null,"Audit a live web page in five phases (catalog, click, trace, classify, report) to identify mock data, hardcoded values, LLM-generated metrics, and broken endpoints. Outputs a markdown report with REAL\u002FMOCK\u002FLLM\u002FHARDCODED\u002FBROKEN\u002FUNKNOWN verdicts per visible value.","Elogic360\u002Fsoftware-factory","Elogic360","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F156535519?v=4","01M74NH3F0RB13PWB7JZDE2V80","elogic360","01M74NH3FPC65082MDZVMFHDM3",0,"MIT","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fmock-hunter\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: mock-hunter\ndescription: \"Audit a live web page in five phases (catalog, click, trace, classify, report) to identify mock data, hardcoded values, LLM-generated metrics, and broken endpoints. Outputs a markdown report with REAL\u002FMOCK\u002FLLM\u002FHARDCODED\u002FBROKEN\u002FUNKNOWN verdicts per visible value.\"\ncategory: testing\nrisk: critical\nsource: community\nsource_repo: CodeShuX\u002Fmockhunter\nsource_type: community\ndate_added: \"2026-05-07\"\nauthor: CodeShuX\ntags: [testing, qa, playwright, mock-detection, web-audit, ai-testing, vibe-coding, claude-code]\ntools: [claude]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002FCodeShuX\u002Fmockhunter\u002Fblob\u002Fmain\u002FLICENSE\"\nplugin:\n  targets:\n    codex: blocked\n    claude: blocked\n---\n\n# MockHunter — Live Page Reality Check\n\n## Overview\n\nMockHunter is a Claude Code skill that audits a live web page and tells you, for every visible value, whether it is real, mocked, LLM-generated, hardcoded, broken, or unknown. It is built for vibe-coded apps (Lovable, Bolt, v0, Replit, AI Studio, Cursor Composer) where the UI may look complete but the data layer often is not. It uses Playwright MCP to drive a real browser, then traces each visible value through the network and DOM to its source.\n\nThis skill adapts the upstream `CodeShuX\u002Fmockhunter` project (community source).\n\nBecause this workflow drives a real browser against live pages, treat it as an interactive audit tool, not a plugin-safe read-only helper. Default to observation-only until the user confirms the target is theirs, identifies a safe test account or environment, and explicitly approves any click, submit, or authenticated action that can mutate state.\n\n## When to Use This Skill\n\n- Use when auditing an AI-generated UI to find out which values are actually wired up\n- Use when reviewing a contractor or teammate's deliverable before sign-off\n- Use before showing a vibe-coded MVP to a customer or investor\n- Use when a dashboard \"looks too clean\" — every metric uniformly round, all timestamps clustered, no variance — and you suspect seeded data\n\n## How It Works\n\n### Phase 1: Setup & Smart Questions\n\n1. Greet the user, ask for the target URL\n2. Auto-detect the stack from the URL (`*.lovable.app`, `*.bolt.new`, `*.v0.app`, `*.replit.app`, `aistudio.google.com`, otherwise Custom)\n3. Ask 3-5 targeted questions: auth mode (public \u002F localhost \u002F form \u002F skip), DB access (optional), suspicions, page goal\n4. Confirm the audit plan, ownership\u002Fpermission, target environment, and allowed action classes before proceeding\n\n### Phase 2: Navigate & Catalog\n\n1. `browser_navigate` to the target URL\n2. Handle auth per chosen mode (form-login: fill fields, click submit)\n3. Wait for network idle (max 10s)\n4. Take full-page screenshot, capture accessibility snapshot\n5. Inventory every: heading, button, link, input, card, badge, stat, table cell, empty state, image\n6. Capture initial console errors and network requests\n\n### Phase 3: Test Interactivity\n\n1. For every tab: click only after the user has approved navigation-style interactions, then snapshot, scroll to bottom, re-catalog\n2. For every button: click only user-approved, allowlisted controls that are clearly non-destructive by role, accessible name, nearby text, icon, URL\u002Faction target, and expected network side effect; skip destructive or ambiguous controls rather than relying on a label regex alone\n3. For every form: identify required fields and prefer empty-submit validation; submit throwaway data only when the user explicitly approved the exact form, target environment, and test account\n4. Record per-element behavior\n\n### Phase 4: Trace Provenance\n\nFor every visible value, run this decision tree:\n\n```\nDid any network request return this value?\n├── YES — found in a response:\n│   ├── Status 4xx\u002F5xx → BROKEN\n│   ├── Endpoint matches \u002Fai|openai|generate|llm|chat → LLM\n│   ├── Response shape matches mock library (faker, MSW, mockoon) → MOCK\n│   ├── Uniformity flags trigger → MOCK or LLM (review)\n│   ├── DB connection provided?\n│   │   ├── Run read-only SELECT, value matches DB row → REAL\n│   │   └── Value not in DB → MOCK\n│   └── No DB → UNKNOWN (best-guess)\n└── NO — value not in any network response:\n    ├── String literal in DOM source → HARDCODED\n    ├── Computed from Math.random \u002F Date.now \u002F faker → MOCK\n    └── Cannot determine → UNKNOWN\n```\n\nUniformity heuristics flag suspicious data:\n- All numeric values identical across rows\n- All percentages round (50%, 75%, 90%)\n- All timestamps cluster within a single minute\n- \u003C 3 unique values across 10+ rows\n\n### Phase 5: Report\n\nGenerate `mockhunter-report.md` with:\n- Summary table (verdict counts)\n- Findings per section\u002Ftab (element \u002F value \u002F verdict \u002F source \u002F severity \u002F action)\n- Console errors and network failures\n- NO-OP buttons\n- Suspicious patterns\n- Smart follow-up questions for the user\n\n## Examples\n\n### Example 1: Auditing a Lovable admin dashboard\n\n```\nUser: \u002Fmockhunter audit https:\u002F\u002Fmy-app.lovable.app\u002Fadmin\nSkill: [Phase 1] Stack detected: Lovable. Auth: skip. DB: no.\n       [Phase 2] Catalog: 6 stat cards, 4 verification queues, 8 activity items.\n       [Phase 3] Search box: NO-OP (zero network requests). Activity link → 404.\n       [Phase 4] Bundle 2.7 MB. Zero \u002Fapi\u002F, zero supabase, zero axios.\n                 \"$42,850\" → string literal in JSX → HARDCODED.\n                 \"+12% vs last month\" → string literal → HARDCODED.\n       [Phase 5] Verdict: 23 HARDCODED, 1 BROKEN, 1 NO-OP, 0 REAL.\n                 Report written to .\u002Fmockhunter-report.md\n```\n\n### Example 2: Public marketing site (mostly real)\n\n```\nUser: \u002Fmockhunter audit https:\u002F\u002Fexample-saas.com\nSkill: ...\n       [Phase 5] Verdict: 8 REAL, 18 HARDCODED (intentional marketing copy),\n                 0 MOCK, 0 BROKEN, 2 UNKNOWN.\n                 No console errors, no broken endpoints.\n```\n\n## Best Practices\n\n- ✅ Provide DB access when available — lifts UNKNOWN verdicts to REAL or MOCK\n- ✅ Use a dedicated test account for form-login auth\n- ✅ Run cold-start tests (zero data) — many vibe-coded apps fail there\n- ✅ Tell the skill if specific sections are intentionally AI-generated, so it doesn't false-flag them\n- ❌ Don't run active interaction on apps you don't own without permission — live clicks and form submissions can mutate state\n- ❌ Don't trust a destructive-button exclusion list by itself — localized labels, icons, aria text, and backend routes can hide mutating actions\n- ❌ Don't trust the audit if the page failed to load — check console first\n\n## Limitations\n\n- Single-page audit per run — no multi-page crawl in v0.1.0\n- Form-login only for auth — no OAuth, magic-link, or 2FA in v0.1.0\n- Caps at ~30 most-prominent buttons per page\n- Markdown report only — no JSON output yet\n- DB verification supports any DB reachable via shell command (psql, mysql, mongosh, wrangler, supabase REST), but not Firestore directly\n\n## Security & Safety Notes\n\n- The skill runs read-only DB SELECTs only, never INSERT\u002FUPDATE\u002FDELETE\n- Skips destructive-looking, ambiguous, icon-only, localized, or external-write controls unless the user has explicitly allowlisted the exact control and environment\n- Never submits forms that look like payment, account deletion, external write operations, account changes, invites, publishing, deployment, messaging, or money movement\n- Uses placeholder credentials (`mockhunter@example.com`) for any throwaway form tests, never the user's real credentials\n- All Playwright actions happen in a controlled MCP browser context — no headless escalation\n","# MockHunter — Live Page Reality Check\n\n## Overview\n\nMockHunter is a Claude Code skill that audits a live web page and tells you, for every visible value, whether it is real, mocked, LLM-generated, hardcoded, broken, or unknown. It is built for vibe-coded apps (Lovable, Bolt, v0, Replit, AI Studio, Cursor Composer) where the UI may look complete but the data layer often is not. It uses Playwright MCP to drive a real browser, then traces each visible value through the network and DOM to its source.\n\nThis skill adapts the upstream `CodeShuX\u002Fmockhunter` project (community source).\n\nBecause this workflow drives a real browser against live pages, treat it as an interactive audit tool, not a plugin-safe read-only helper. Default to observation-only until the user confirms the target is theirs, identifies a safe test account or environment, and explicitly approves any click, submit, or authenticated action that can mutate state.\n\n## When to Use This Skill\n\n- Use when auditing an AI-generated UI to find out which values are actually wired up\n- Use when reviewing a contractor or teammate's deliverable before sign-off\n- Use before showing a vibe-coded MVP to a customer or investor\n- Use when a dashboard \"looks too clean\" — every metric uniformly round, all timestamps clustered, no variance — and you suspect seeded data\n\n## How It Works\n\n### Phase 1: Setup & Smart Questions\n\n1. Greet the user, ask for the target URL\n2. Auto-detect the stack from the URL (`*.lovable.app`, `*.bolt.new`, `*.v0.app`, `*.replit.app`, `aistudio.google.com`, otherwise Custom)\n3. Ask 3-5 targeted questions: auth mode (public \u002F localhost \u002F form \u002F skip), DB access (optional), suspicions, page goal\n4. Confirm the audit plan, ownership\u002Fpermission, target environment, and allowed action classes before proceeding\n\n### Phase 2: Navigate & Catalog\n\n1. `browser_navigate` to the target URL\n2. Handle auth per chosen mode (form-login: fill fields, click submit)\n3. Wait for network idle (max 10s)\n4. Take full-page screenshot, capture accessibility snapshot\n5. Inventory every: heading, button, link, input, card, badge, stat, table cell, empty state, image\n6. Capture initial console errors and network requests\n\n### Phase 3: Test Interactivity\n\n1. For every tab: click only after the user has approved navigation-style interactions, then snapshot, scroll to bottom, re-catalog\n2. For every button: click only user-approved, allowlisted controls that are clearly non-destructive by role, accessible name, nearby text, icon, URL\u002Faction target, and expected network side effect; skip destructive or ambiguous controls rather than relying on a label regex alone\n3. For every form: identify required fields and prefer empty-submit validation; submit throwaway data only when the user explicitly approved the exact form, target environment, and test account\n4. Record per-element behavior\n\n### Phase 4: Trace Provenance\n\nFor every visible value, run this decision tree:\n\n```\nDid any network request return this value?\n├── YES — found in a response:\n│   ├── Status 4xx\u002F5xx → BROKEN\n│   ├── Endpoint matches \u002Fai|openai|generate|llm|chat → LLM\n│   ├── Response shape matches mock library (faker, MSW, mockoon) → MOCK\n│   ├── Uniformity flags trigger → MOCK or LLM (review)\n│   ├── DB connection provided?\n│   │   ├── Run read-only SELECT, value matches DB row → REAL\n│   │   └── Value not in DB → MOCK\n│   └── No DB → UNKNOWN (best-guess)\n└── NO — value not in any network response:\n    ├── String literal in DOM source → HARDCODED\n    ├── Computed from Math.random \u002F Date.now \u002F faker → MOCK\n    └── Cannot determine → UNKNOWN\n```\n\nUniformity heuristics flag suspicious data:\n- All numeric values identical across rows\n- All percentages round (50%, 75%, 90%)\n- All timestamps cluster within a single minute\n- \u003C 3 unique values across 10+ rows\n\n### Phase 5: Report\n\nGenerate `mockhunter-report.md` with:\n- Summary table (verdict counts)\n- Findings per section\u002Ftab (element \u002F value \u002F verdict \u002F source \u002F severity \u002F action)\n- Console errors and network failures\n- NO-OP buttons\n- Suspicious patterns\n- Smart follow-up questions for the user\n\n## Examples\n\n### Example 1: Auditing a Lovable admin dashboard\n\n```\nUser: \u002Fmockhunter audit https:\u002F\u002Fmy-app.lovable.app\u002Fadmin\nSkill: [Phase 1] Stack detected: Lovable. Auth: skip. DB: no.\n       [Phase 2] Catalog: 6 stat cards, 4 verification queues, 8 activity items.\n       [Phase 3] Search box: NO-OP (zero network requests). Activity link → 404.\n       [Phase 4] Bundle 2.7 MB. Zero \u002Fapi\u002F, zero supabase, zero axios.\n                 \"$42,850\" → string literal in JSX → HARDCODED.\n                 \"+12% vs last month\" → string literal → HARDCODED.\n       [Phase 5] Verdict: 23 HARDCODED, 1 BROKEN, 1 NO-OP, 0 REAL.\n                 Report written to .\u002Fmockhunter-report.md\n```\n\n### Example 2: Public marketing site (mostly real)\n\n```\nUser: \u002Fmockhunter audit https:\u002F\u002Fexample-saas.com\nSkill: ...\n       [Phase 5] Verdict: 8 REAL, 18 HARDCODED (intentional marketing copy),\n                 0 MOCK, 0 BROKEN, 2 UNKNOWN.\n                 No console errors, no broken endpoints.\n```\n\n## Best Practices\n\n- ✅ Provide DB access when available — lifts UNKNOWN verdicts to REAL or MOCK\n- ✅ Use a dedicated test account for form-login auth\n- ✅ Run cold-start tests (zero data) — many vibe-coded apps fail there\n- ✅ Tell the skill if specific sections are intentionally AI-generated, so it doesn't false-flag them\n- ❌ Don't run active interaction on apps you don't own without permission — live clicks and form submissions can mutate state\n- ❌ Don't trust a destructive-button exclusion list by itself — localized labels, icons, aria text, and backend routes can hide mutating actions\n- ❌ Don't trust the audit if the page failed to load — check console first\n\n## Limitations\n\n- Single-page audit per run — no multi-page crawl in v0.1.0\n- Form-login only for auth — no OAuth, magic-link, or 2FA in v0.1.0\n- Caps at ~30 most-prominent buttons per page\n- Markdown report only — no JSON output yet\n- DB verification supports any DB reachable via shell command (psql, mysql, mongosh, wrangler, supabase REST), but not Firestore directly\n\n## Security & Safety Notes\n\n- The skill runs read-only DB SELECTs only, never INSERT\u002FUPDATE\u002FDELETE\n- Skips destructive-looking, ambiguous, icon-only, localized, or external-write controls unless the user has explicitly allowlisted the exact control and environment\n- Never submits forms that look like payment, account deletion, external write operations, account changes, invites, publishing, deployment, messaging, or money movement\n- Uses placeholder credentials (`mockhunter@example.com`) for any throwaway form tests, never the user's real credentials\n- All Playwright actions happen in a controlled MCP browser context — no headless escalation\n",{"name":5,"risk":24,"tags":25,"tools":34,"author":36,"plugin":37,"source":40,"license":15,"category":26,"date_added":41,"description":7,"source_repo":42,"source_type":40,"license_source":43},"critical",[26,27,28,29,30,31,32,33],"testing","qa","playwright","mock-detection","web-audit","ai-testing","vibe-coding","claude-code",[35],"claude","CodeShuX",{"targets":38},{"codex":39,"claude":39},"blocked","community","2026-05-07","CodeShuX\u002Fmockhunter","https:\u002F\u002Fgithub.com\u002FCodeShuX\u002Fmockhunter\u002Fblob\u002Fmain\u002FLICENSE","main","c475fc64e94e803b50d14a791dfee8853fbb2c5c","integrations\u002Fantigravity-skills\u002Fskills\u002Fmock-hunter","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory","https:\u002F\u002Fgithub.com\u002FElogic360","2026-11-08 22:21:22",{"source":8,"skillName":5,"commands":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add Elogic360\u002Fsoftware-factory --skill mock-hunter",{"tool":56,"command":57},"bunx","bunx skills add Elogic360\u002Fsoftware-factory --skill mock-hunter",{"tool":59,"command":60},"pnpm","pnpm dlx skills add Elogic360\u002Fsoftware-factory --skill mock-hunter","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fintegrations\u002Fantigravity-skills\u002Fskills\u002Fmock-hunter\u002FSKILL.md",true,[],[65,73,80,87,94,101],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":19},"01M79G206MT3J6S0GY3C45P2KV","vss-summarize-video","Use to summarize a recorded video via the LVS summarization microservice (HITL-gated) with a VLM fallback. Not for report generation or live RTSP captioning.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-summarize-video\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":19},"01M79G1WN63PGRE8CKD47WEBQ5","vss-setup-video-analytics-api","Use to deploy the vss-video-analytics-api REST service standalone (config-source, data-log bind, Elasticsearch, optional Kafka). Not for full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-video-analytics-api\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":19},"01M79G1S9F7VY3EF6H53PRP5AN","vss-setup-behavior-analytics","Use to deploy the vss-behavior-analytics service standalone (entrypoint, config-source, optional calibration). Not for the full warehouse deploy.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-setup-behavior-analytics\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79G1N1S1Y27PFZPYMNK1MTQ","vss-search-archive","Use this skill to run top-level VSS fusion search on archived video, or to ingest video files \u002F RTSP streams for search. Do NOT use for ad-hoc visual Q&A (use vss-ask-video), live captioning (use vss-deploy-dense-captioning), or video summarization and reports (use vss-summarize-video).","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-search-archive\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79G1H6WN0Q6C0VCAXCZX6B7","vss-query-analytics","Use this skill when reading video-analytics metrics, incidents, alerts, and sensor data via the VA-MCP server (port 9901). Not for live VLM or incident-range narrative reports.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-query-analytics\u002FSKILL.md",[],[],{"skillNo":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":69,"licenseFileUrl":6,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":19},"01M79G1DYPNXQS7QHZ0AAF5FX5","vss-manage-video-io-storage","Use to call the VIOS REST API (sensor list, timelines, clip extraction, snapshots, add\u002Fdelete sensors and streams). Not for VLM inference or search.","https:\u002F\u002Fgithub.com\u002FElogic360\u002Fsoftware-factory\u002Fblob\u002Fmain\u002Fskills\u002Fnvidia\u002Fvss-manage-video-io-storage\u002FSKILL.md",[],[]]