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/ceilf6/frontagent/requirement-interviewernpx skills add ceilf6/FrontAgent --skill requirement-interviewergit clone --depth 1 https://github.com/ceilf6/FrontAgentWrote 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/ceilf6/frontagent/requirement-interviewer)<a href="https://agentmods.dev/skills/ceilf6/frontagent/requirement-interviewer"><img src="https://agentmods.dev/badge/skills/ceilf6/frontagent/requirement-interviewer.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.00054 | $0.00389 |
| Opus 5 | $0.00027 | $0.00195 |
| Sonnet 5 | $0.00011 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
requirement-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 4d 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
Requirement Interviewer
Collect missing constraints through phased questioning. Refuse to plan, code, or propose irreversible implementation details until the required answers are complete.
Workflow
- Read
references/question-flow.md. - Ask only the next unanswered question cluster, not the whole interview at once.
- Read
references/answer-completeness.mdto decide whether the reply is sufficient or needs follow-up. - Read
references/gating-rules.mdbefore moving from clarification into planning. - After each phase, summarize confirmed facts, explicit assumptions, and open questions.
- Only when all mandatory gates pass, hand off a concise, execution-ready brief or plan.
Interview Contract
- Ask 1-3 short questions at a time.
- Prefer constrained choices when possible.
- Keep questions ordered: objective first, implementation later.
- If the user says "you decide", record the default explicitly as an assumption.
- Separate confirmed requirements from inferred assumptions.
Guardrails
- Do not generate code, file edits, or architecture proposals before gates pass.
- Do not ask duplicate questions.
- Do not jump into low-level implementation details before product intent is clear.
- Do not silently fill critical gaps with guesses.
- Stop and ask for explicit approval when the decision changes scope, cost, or stack direction.
What ships with it
4 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.
- 4d ago First seen · 44 lines · 54 tokens per session scan A 424a38059fee
requirement-interviewer is a skill published in the GitHub repository ceilf6/FrontAgent (117 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 389 once invoked, about $0.0003 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-30.
Other skills, from other repositories
maintain-model-list
Maintain the supported LLM model list: add a new model, or run routine maintenance to verify availability and discover new models worth adding. Use when the user asks to add/support a model, update the model list, or check model availability.
update-changelog
Update docs/CHANGELOG.md from git history, GitHub releases, and code diffs. Use when: writing release notes, syncing the latest changelog entry, summarizing a new tag, or keeping changelog wording concise and consistent.
git-cleanup
Clean up local git branches and remotes accumulated from PR reviews. Use when the user asks to clean branches, remove stale remotes, or tidy up the local git state.
submit-pr-from-current-changes
Create a branch, commit existing local changes, push them, and open a pull request. Use when submitting current work as a PR.
pre-impl-discussion
Conduct a thorough pre-implementation discussion before making significant changes. Use when the user wants to discuss, plan, or evaluate a change before implementing it — especially when they say words like 'discuss', 'evaluate', 'plan', or 'let's talk about'.
agent-spec-tool-first
CRITICAL: Use for agent-spec CLI tool workflow. Triggers on: agent-spec, contract, lifecycle, guard, verify, explain, stamp, checkpoint, plan, requirements, work-units, knowledge requirements, KLL, docs vs knowledge, spec verification, task contract, spec quality, lint spec, run log, "how to verify", "how to use…