Quality checks for AI coding agents — find the bugs Claude / Cursor / Codex tend to ship before they reach prod. Pick the install path that matches where you use Claude.
Single file. Drag into Claude Desktop's plugin manager. Prompts surface in the + attachments menu.
↓ Download & install+ button → pick a Jank prompt (jank, jank_light, …).Note: Claude Desktop's main chat does not surface DXT prompts in the typed-slash / autocomplete — only via the + picker. For typed /jank, use the marketplace install on the right.
curl -L -o jank.dxt https://jank.ai/extension/jank-latest.dxt open jank.dxt
Bare /jank, /jank_light, … appear in the typed-slash menu of Claude Desktop's Code tab.
Copy & paste, then ⌘Q + relaunch:
git clone https://github.com/jarbon/jank.git /tmp/jank mkdir -p ~/.claude/plugins ~/.claude/commands cp -r /tmp/jank/plugins/jank-plugin ~/.claude/plugins/ ln -sf ~/.claude/plugins/jank-plugin/commands/*.md ~/.claude/commands/ rm -rf /tmp/jank
/jankfull sweep
/jank_lightstatic scan
/jank_testtest one feature
/jank_explore5 user personas
/jank_cloudhosted audit
/jank_cleanreap zombie Chrome
~/.claude/plugins/, and symlinks the slash-command bodies into ~/.claude/commands/./ — the six commands appear in the slash menu.rm -f ~/.claude/commands/jank*.md rm -rf ~/.claude/plugins/jank-plugin
Almost always: Claude Desktop wasn't fully quit after install. ⌘Q (not just close-window),
wait a couple seconds, relaunch. New conversation → type /.
If still missing, verify ls ~/.claude/commands/jank.md exists for the Code-tab install,
or check Settings → Extensions for the DXT install.
The MCP server crashed or wasn't started. ⌘Q + relaunch usually fixes it.
For the bundled server file: ls ~/.claude/plugins/jank-plugin/server/index.js — if missing, re-run the install.
Check the log: tail -40 "~/Library/Logs/Claude/mcp-server-Jank — AI quality checks.log".
Two LLMs run during a local /jank run: chat Claude (handles orchestration — billed against your Claude account, ~5–15 calls per run)
and your configured provider (OpenAI / Anthropic / Gemini / Azure — handles persona reasoning, billed against that provider).
Per-command provider call budget (very approximate, varies with model + page complexity):
/jank_light — 1–3 calls · ~10–30k tokens/jank — ~80–120 calls (10 personas × ~6 steps each) · ~300–700k tokens/jank_test — ~10–25 calls (2 focused agents) · ~50–150k tokens/jank_explore — ~30–60 calls (5 personas × ~5–6 steps) · ~150–400k tokens/jank_cloud — 0 local LLM calls (cloud-side, billed by your jank.ai plan)/jank_clean — 0 LLM calls
Rough cost for a typical /jank run:
gpt-5.4-mini ≈ $0.05–$0.20 · claude-sonnet-4-6 ≈ $0.50–$1.50 · gemini-3-flash-preview ≈ under $0.05.
/jank_light and /jank_clean are essentially free; /jank_cloud is free for the first 3 runs/month.
DXT install: Settings → Extensions → Jank → fields for OpenAI, Anthropic, Gemini, Azure keys + a default-provider picker.
Code-tab install: tell Claude "save my OpenAI key sk-…" — it'll call the jank_config tool.
Env vars: OPENAI_API_KEY, ANTHROPIC_API_KEY, GEMINI_API_KEY, AZURE_OPENAI_API_KEY.
You only need one provider. /jank_light and /jank_cloud don't need a local LLM key at all.
Restart the MCP server so the new env vars (or saved config) are picked up: ⌘Q Claude Desktop, relaunch.
Verify it landed: in chat, ask Claude to call jank_get_config — it'll show the saved email + masked api_key + source ("env" / "disk" / "unset").
~/.config/jank/config.json — provider keys, jank.ai email, default settings.
~/.claude/plugins/jank-plugin/ — the plugin itself (Code-tab install).
~/.claude/commands/jank*.md — slash-command shims (Code-tab install).
~/.jank/runs/<timestamp>/ — screenshots + findings from past runs (safe to delete any time).
DXT: download jank-latest.dxt, drag-drop, ⌘Q + relaunch. Settings → Extensions → Jank → Remove first if you have an older version.
Code tab: re-run the 4-line clone install above. The cp -r overwrites the existing plugin directory; symlinks repoint automatically.
DXT: Settings → Extensions → Jank → Remove. ⌘Q + relaunch.
Code tab:
rm -f ~/.claude/commands/jank*.md rm -rf ~/.claude/plugins/jank-plugin # optional: also remove saved config rm -rf ~/.config/jank ~/.jank
After install, open Settings → Extensions → Jank. You'll see two fields: Email (used by /jank_cloud) and API Key (only needed past the free tier). Save and restart — the values flow into the MCP server automatically.
No settings UI here — set once via Claude. In a Code-tab session, run:
Save my jank.ai email as you@example.com (call jank_set_config with that email).
Persists to ~/.config/jank/config.json. Subsequent /jank_cloud <url>
calls auto-fill your email. Free tier (3 reports/month) needs no API key.