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/ttxttx1111/sts2-llm/interviewnpx skills add ttxttx1111/sts2-llm --skill interviewgit clone --depth 1 https://github.com/ttxttx1111/sts2-llmWrote 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/ttxttx1111/sts2-llm/interview)<a href="https://agentmods.dev/skills/ttxttx1111/sts2-llm/interview"><img src="https://agentmods.dev/badge/skills/ttxttx1111/sts2-llm/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.00034 | $0.00512 |
| Opus 5 | $0.00017 | $0.00256 |
| Sonnet 5 | $0.00007 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Skill
Read the plan file at $ARGUMENTS and conduct an exhaustive interview using the AskUserQuestion tool.
Critical Instructions
ASK MANY QUESTIONS. This is not a quick review — it's a thorough interrogation of the design. 10, 15, 20+ questions is normal and expected. Do NOT rush. Do NOT summarize early. Keep asking until EVERY ambiguity is resolved.
After EACH answer:
- Dig deeper with follow-up questions on that topic
- Surface implications the user may not have considered
- Only move to the next topic when the current one is fully explored
You are done when:
- Every technical decision has a clear rationale
- Every edge case has a defined behavior
- Every integration point is specified
- You cannot think of any more meaningful questions to ask
Use your judgment — when answers start feeling complete and consistent, and you've covered all the topics below, wrap up and write the final spec. But if in doubt, ask another question.
Interview Topics (Cover ALL of These)
- Technical implementation details (data structures, algorithms, system interactions)
- MCP protocol specifics (tool schemas, resource URIs, error responses)
- CommunicationMod integration (state handling, command timing, error recovery)
- Edge cases and error handling (what happens when things go wrong?)
- Testing strategy (unit tests, integration tests, mock game state)
- Risks and mitigation
- Future extensibility (how might this need to change later?)
- Dependencies and ordering (what needs to exist first?)
Process
- Read the specified plan file thoroughly
- Identify ALL ambiguous or underspecified areas
- Use AskUserQuestion with 2-4 focused options per question
- After each answer, ask follow-up questions to go deeper
- Continue interviewing until the user confirms completion
- Update the plan file with the complete, detailed specification
Anti-Patterns to Avoid
- Asking only 3-5 surface-level questions
- Accepting vague answers without digging deeper
- Moving on before a topic is fully explored
- Summarizing and finishing early to "save time"
- Assuming you know what the user wants
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 · 57 lines · 34 tokens per session scan A 433e0b0093da
interview is a skill published in the GitHub repository ttxttx1111/sts2-llm (41 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 512 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-30.
Other skills, from other repositories
microsoft-build
Your companion for Microsoft Build 2026. Helps you find sessions relevant to your project, discover what's new for your tech stack, scaffold projects from sessions, and plan your event schedule. Activate when users mention sessions, schedule, what's new, Build, Ignite, AI Tour, Microsoft event, conference, or…
speckit-init
Scaffold a Spec Kit (spec-driven development) project for GitHub Copilot by running specify init --integration copilot --integration-options="--skills". USE FOR: starting a new spec-kit project, bootstrapping spec-driven development in an existing repo, installing spec-kit templates/scripts/commands for Copilot. DO…
speckit-bundle
Discover, install, and author Spec Kit bundles via specify bundle. USE FOR: searching/showing/listing bundles, installing/updating/removing a bundle (a curated set of extensions/presets/integrations/workflows), validating a bundle manifest, building a distributable bundle artifact, initializing a project and…
speckit-extension
Manage Spec Kit extensions via specify extension. USE FOR: installing/removing/updating spec-kit extensions, searching the extension catalog, showing extension info, enabling/disabling extensions, setting extension resolution priority, managing extension catalogs. DO NOT USE FOR: presets (use speckit-preset), bundles…
speckit-preset
Manage Spec Kit presets via specify preset. USE FOR: installing/removing presets, searching the preset catalog, showing preset info, resolving which template a preset name maps to, enabling/disabling presets, setting preset resolution priority, managing preset catalogs. DO NOT USE FOR: extensions (use…
speckit-workflow
Manage and run Spec Kit automation workflows via specify workflow. USE FOR: running a workflow by ID or local YAML, resuming a paused/failed run, checking run status, listing/installing/removing workflows, searching the workflow catalog, showing a workflow step graph. DO NOT USE FOR: extensions (use…