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.
npx agentmods add skills/gzupark/claude-plugin-pack/plan-interviewnpx skills add GzuPark/claude-plugin-pack --skill plan-interviewgit clone --depth 1 https://github.com/GzuPark/claude-plugin-packWrote 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/skills/gzupark/claude-plugin-pack/plan-interview)<a href="https://agentmods.dev/skills/gzupark/claude-plugin-pack/plan-interview"><img src="https://agentmods.dev/badge/skills/gzupark/claude-plugin-pack/plan-interview.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00039 | $0.00770 |
| Opus 5 | $0.00019 | $0.00385 |
| Sonnet 5 | $0.00008 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
plan-interview 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Interview
Conduct in-depth technical interviews about project plans to deeply understand implementation details, uncover hidden assumptions, and identify potential issues before implementation begins.
Language: Match the user's input language. Use explicitly requested language if specified.
Workflow
Step 1: Understand Input
Input: $ARGUMENTS
- File path (contains
/or ends with.md,.txt) -> Read the file, use Glob for related files - Text description -> Use directly as project concept
Step 2: Assess Complexity
| Complexity | Indicators | Questions |
|---|---|---|
| Simple | Single feature, clear scope | 3-4 |
| Medium | Multiple features, some integrations | 5-7 |
| Complex | System-wide, many integrations | 8-10 |
Step 3: Conduct Interview
Use AskUserQuestion tool. Ask ONE question at a time.
For question areas, see references/interview-areas.md.
Progress Tracking: Display after each question:
[Progress: 2/6 | Covered: Architecture, API | Remaining: Security, Testing]
Guidelines:
- Ask meaningful follow-up questions
- Dig deeper on vague answers
- Challenge assumptions respectfully
- Skip non-applicable areas
Intermediate Save: Every 3-4 questions,
save to .interview-progress-<timestamp>.md:
- Questions asked and responses
- Areas covered and remaining
Completion: Interview ends when:
- All relevant areas covered, OR
- Maximum questions (10) reached, OR
- User requests to end
Before ending: "I've covered [areas]. Anything else before writing the specification?"
Step 4: Write Specification
Use template from references/spec-template.md.
Output location:
- File input -> Same directory with
-specsuffix - Text input -> Ask user, default
./specs/<project-name>-spec.md
Cleanup: Delete .interview-progress-*.md after successful spec generation.
What ships with it
2 files beside SKILL.md 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.
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.
- 3d ago First seen · 125 lines · 39 tokens per session scan A 13464fa044d0
plan-interview is a skill published in the GitHub repository GzuPark/claude-plugin-pack (6 stars, last pushed 7mo ago), licensed MIT. It adds 39 tokens to every session and 770 once invoked, about $0.0002 per session on Opus 5. 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…