mockhunter

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.

Security

Grade A, and why

mockhunter 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 yesterday.

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.

.claude-plugin/marketplace.json · 37 lines

What it actually says

{
  "name": "mockhunter",
  "owner": {
    "name": "CodeShuX",
    "url": "https://github.com/CodeShuX"
  },
  "metadata": {
    "description": "MockHunter — Claude Code skill that audits live web pages for mock data, hardcoded values, and broken endpoints via Playwright.",
    "version": "0.1.1"
  },
  "plugins": [
    {
      "name": "mockhunter",
      "source": "./",
      "description": "Audit live web pages for fake/mock data — 5-phase Playwright + Claude Code skill that classifies every visible value as REAL, MOCK, LLM, HARDCODED, BROKEN, or UNKNOWN. Targets vibe-coded apps (Lovable, Bolt, v0, Replit, AI Studio, Cursor Composer).",
      "version": "0.1.1",
      "author": {
        "name": "CodeShuX",
        "url": "https://github.com/CodeShuX"
      },
      "homepage": "https://github.com/CodeShuX/mockhunter",
      "repository": "https://github.com/CodeShuX/mockhunter",
      "license": "MIT",
      "category": "testing",
      "tags": [
        "testing",
        "qa",
        "playwright",
        "mock-detection",
        "web-audit",
        "ai-testing",
        "vibe-coding"
      ]
    }
  ]
}

Files

What ships with it

1 file beside marketplace.json in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

Related

Other plugins, from other repositories