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/waazy-w/claude-phantomWrote 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/plugins/waazy-w/claude-phantom/plugin)<a href="https://agentmods.dev/plugins/waazy-w/claude-phantom/plugin"><img src="https://agentmods.dev/badge/plugins/waazy-w/claude-phantom/plugin/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/plugins/waazy-w/claude-phantom/plugin"><img src="https://agentmods.dev/badge/plugins/waazy-w/claude-phantom/plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
phantom 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.
What it actually says
{
"name": "phantom",
"version": "0.7.0",
"description": "Crash recovery procedure for Claude Code: diagnose, write a failing test, patch minimally, verify, write a post-mortem.",
"author": { "name": "claude-phantom contributors" },
"skills": "./skills/",
"commands": "./commands/"
}
What it installs
The manifest is a name and a version. 1 skill, 1 command, 3 hooks travel with it, and installing the plugin installs all of them — 87 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 9 lines scan A 78ac76815a9d
phantom is a plugin published in the GitHub repository waazy-w/claude-phantom (4 stars, last pushed 1mo ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-08-31.
Other plugins, from other repositories
sqry
AST-based semantic code search (compiler-grade, not embeddings). Skills + MCP (sqry-mcp) + LSP (sqry-lsp) for Grok Build, Claude Code, and compatible agents. 37 languages, 39 tools, live resources from sqry-mcp binary.
polygraph
A polygraph for your state machine. The agent does the hard part for you: it instruments your code, builds any test doubles needed to run it, and captures real execution traces — then has an LLM derive a transition-function spec from the source (default: a SAM v2 strict-profile module with named…
ci-incident-medic
Triages failing GitHub Actions runs, hardens Dockerfiles, pre-flights Kubernetes manifests before they reach the cluster, and drafts blameless postmortems from incident evidence.
xcode-cli
Xcode CLI — Build, test, run, and manage Xcode projects from Claude Code.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.