agentmods.dev

claude-spec-interviewer

claude-spec-interviewer is a skill for Claude Code, Codex from stark-ai-de/agent-skills. It costs 105 tokens per session (3,029 once invoked), scanned A, original, Apache-2.0.

An interview workflow that turns an unclear Claude Code request into a checked implementation specification. The specification records the scope, decisions, assumptions, validation plan, and execution instructions before coding begins.

In plain words
What is it for?
Use it when a Claude Code task spans multiple files, involves trade-offs, or needs acceptance criteria and validation commands. It is meant for planning features, fixes, refactors, migrations, and architecture work.
Why use it?
It removes ambiguity from requests that could otherwise lead to incorrect scope or missed requirements. It also checks proposed decisions against the repository and relevant sources.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; mentions CLAUDE.md; names the AskUserQuestion tool.

not rated 5repo today A scan 105 tokens original Apache-2.0

Good fit Use it when a Claude Code task spans multiple files, involves trade-offs, or needs acceptance criteria and validation commands. It is meant for planning features, fixes, refactors, migrations, and architecture work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/stark-ai-de/agent-skills/claude-spec-interviewer
View source ↗ stark-ai-de/agent-skills stark-ai-de.github.io
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.

Any agent
npx skills add stark-ai-de/agent-skills --skill claude-spec-interviewer
Clone the repo
git clone --depth 1 https://github.com/stark-ai-de/agent-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for claude-spec-interviewer

README.md
[![agentmods](https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/claude-spec-interviewer/github.svg)](https://agentmods.dev/skills/stark-ai-de/agent-skills/claude-spec-interviewer)
Your own site
<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/claude-spec-interviewer"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/claude-spec-interviewer/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.

agentmods 80×15 button for claude-spec-interviewer

Your own site · 80×15
<a href="https://agentmods.dev/skills/stark-ai-de/agent-skills/claude-spec-interviewer"><img src="https://agentmods.dev/badge/skills/stark-ai-de/agent-skills/claude-spec-interviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 105 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,029 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00105 $0.03029
Opus 5 $0.00053 $0.01515
Sonnet 5 $0.00021 $0.00606
Haiku 4.5 $0.00011 $0.00303

Measured 11d ago against content hash 46f7fed25e82, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

claude-spec-interviewer 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 11d 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.

skills/claude-operations/claude-spec-interviewer/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Spec Interviewer

Goal

Produce a user-verified implementation spec with bounded scope, explicit assumptions and validation, a source challenge, and ADRs for durable decisions when needed. Save it using the repo's confirmed convention; save ADRs only when the ADR gate requires them.

This is one end-to-end outcome, not a public multi-workflow skill. Do not invent review/save variants or add a workflow-selection checkpoint.

When to use

  • The user has a rough idea but not a production-ready implementation spec.
  • The task spans multiple files or concerns, or requires tradeoff decisions.
  • The request needs acceptance criteria, validation commands, rollout notes, or risk handling.
  • The user wants a reusable written artifact before implementation begins.
  • The user invokes /claude-spec-interviewer or asks Claude Code to plan before coding.
  • Requirements, feature shape, ADR assumptions, or the implementation approach should be challenged against repo reality and current external sources before coding.

When not to use

  • The user already provided a complete implementation spec with files, constraints, tests, and acceptance criteria.
  • The task is a tiny one-file edit without meaningful ambiguity.
  • The user wants brainstorming only and no concrete implementation artifact.
  • The user only wants a Claude Code rule, command, or other prompt-scope file authored, not an implementation spec.
  • The task is primarily a policy, legal, or business-decision document.
  • The user asks to audit or clean up Claude Code memory, Codex memory, or Cursor rules state; use the matching memory or rules skill instead.

Inputs to inspect

  • The current user request and any follow-up answers.
  • Relevant AGENTS.md, CLAUDE.md, CLAUDE.local.md, .claude/CLAUDE.md, .claude/rules/**/*.md, ~/.claude/rules/**/*.md, README.md, issue descriptions, ADRs, repo docs, and docs/agents/ files.
  • Existing specs, plans, requirements, and PRDs the user wants preserved or challenged.
  • File layout, naming conventions, scripts, package manager, lint/test/type-check commands, and CI expectations.
  • Current framework, library, API, or platform documentation through available MCP tools or web search when a decision depends on up-to-date behavior.
  • Error messages, screenshots, logs, PR feedback, or example files the user supplied.
  • Claude Code project or personal skill folders such as .claude/skills/ and ~/.claude/skills/ only when the spec depends on local Claude Code skill behavior.
  • Claude Code auto-memory evidence only when it is surfaced by the user, available through /memory, or materially relevant to the requested implementation plan.

Read the full file on GitHub · 146 lines

Files

What ships with it

12 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.

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.

  1. 11d ago First seen · 146 lines · 105 tokens per session scan A 46f7fed25e82

Subscribe to this mod's changes

claude-spec-interviewer is a skill published in the GitHub repository stark-ai-de/agent-skills (5 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 3,029 once invoked, about $0.0005 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.

Planningadragent-skillsai-agentscodexdeveloper-toolsopenai-codex
Related

Other skills, from other repositories

openlore-brainstorm

Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.

clay-good/OpenLore · 40 tokens

openlore-execute-refactor

Apply a confirmed .openlore/refactor-plan.md with a test gate after each change. Use when asked to execute or continue an OpenLore refactoring plan.

clay-good/OpenLore · 41 tokens

openlore-plan-refactor

Identify a high-priority refactoring target, assess its blast radius, and write .openlore/refactor-plan.md without changing code. Use when asked to plan or prioritize a refactor.

clay-good/OpenLore · 46 tokens

openlore-debug

Debug with OpenLore structural context, an explicit root-cause hypothesis, and RED/GREEN verification. Use when a bug, failure, or regression needs diagnosis and repair.

clay-good/OpenLore · 39 tokens

openlore-implement-story

Implement a brownfield story with OpenLore orientation, risk checks, spec validation, tests, and drift detection. Use when asked to implement or continue a story in an existing codebase.

clay-good/OpenLore · 44 tokens

openlore-write-tests

Write and run real tests for a function or spec scenario after reading implementation and contract evidence. Use when asked to add, improve, or repair tests without stubs or placeholders.

clay-good/OpenLore · 41 tokens