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/viktorbezdek/skillstack/interview-facilitationnpx skills add viktorbezdek/skillstack --skill interview-facilitationgit clone --depth 1 https://github.com/viktorbezdek/skillstackWhat 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.00172 | $0.02509 |
| Opus 5 | $0.00086 | $0.01255 |
| Sonnet 5 | $0.00034 | $0.00502 |
| Haiku 4.5 | $0.00017 | $0.00251 |
Grade A, and why
interview-facilitation 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 2d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Facilitation
A swarm interview is choreography, not free-for-all. Without structure, six personas talking at once is six monologues. With structure, it's a roundtable.
This skill covers the interview arc — how the swarm's questions are sequenced, how depth and breadth trade off, and how the user is given enough air to think between rounds.
Core principle
Diverge first, converge last. The first round of questions should open the topic from many angles (each persona surfacing different concerns). The closing round should narrow to specific decisions. In between, the orchestrator decides whether one or two areas need deeper probing.
The three-phase arc
A well-facilitated swarm interview has three phases:
Phase 1 — Divergent opening (one swarm round)
All personas spawn in parallel. Each surfaces their core questions, concerns, and observations. The user receives a synthesis covering breadth across all spawned personas.
This is the only round many brainstorms need. For a focused decision, opening + synthesis is sometimes enough.
Phase 2 — Targeted probing (optional second round)
If synthesis surfaced 1-2 areas of significant disagreement or critical open questions, spawn a focused second round with just the personas in tension on those specific issues.
Examples:
- "Round 1 PM said 'ship default-on'; Skeptic said 'opt-in is safer'. Round 2: spawn just PM and Skeptic to argue this specific point."
- "Round 1 Pre-Mortem named a critical failure mode; Operator confirmed. Round 2: spawn Engineer + Operator to work through mitigation."
Phase 3 — Convergent closing (one swarm round, narrow scope)
If the brainstorm produced a tentative direction, spawn a tight closing round to pressure-test the proposed decision. Usually 3-4 personas: Skeptic + relevant domain experts.
Closing prompt format: "Given that we're leaning toward [decision], each of you: name the strongest case AGAINST this and the strongest case FOR. One paragraph each."
What ships with it
5 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.
- 2d ago First seen · 257 lines · 172 tokens per session scan A c8c300b76e1a
interview-facilitation is a skill published in the GitHub repository viktorbezdek/skillstack (11 stars, last pushed 2mo ago), licensed MIT. It adds 172 tokens to every session and 2,509 once invoked, about $0.0009 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
gossipcat
Use when installing or setting up gossipcat multi-agent orchestration (parallel review, consensus, adaptive dispatch) in Claude Code or Cursor. Installs the gossipcat MCP server and hands off to gossipstatus() for all live rules.
Elephant Agent
Complete guide to what Elephant Agent is, how to use it from the CLI, how herd, wake, Personal Model, proactive curiosity, skills, and tools fit together, and how to explain Elephant Agent clearly to users, contributors, or evaluators.
libretranslate-markdown-i18n
Machine-translate Markdown / Obsidian / Quartz content into other languages using a self-hosted LibreTranslate instance, preserving frontmatter, headings, emojis, bold/italic, wikilinks (![[...]]/[[...]]) and internal links. Use whenever a user wants to auto-translate a Markdown vault, Obsidian notes, or a…
awesome-skills-master
Master catalog orchestrator and autonomous installer for AI agents. Use when exploring, cloning, discovering, or installing skills, plugins, or MCP servers from awesome-skills without using interactive CLI tools. Guides environment detection, rule adaptation (.mdc/CLAUDE.md), MCP configuration, and strict author…
readme-template
Standard README template for repos — professional structure with badges, overview, table of contents, features/modules, stack, installation, configuration, tests, security, structure, docs, roadmap, contribute, license, author + RepoActivity sections (Star History, repo stats) + profile GIF footer. Use when creating…
docker-single-port-multi-instance
Consolidate multiple Docker Compose app instances (production / test / demo) behind ONE host port using an nginx reverse proxy that routes by URL path prefix (e.g. /demo). Use when a user wants 'one port, several apps/banks' or a demo reachable simultaneously from the main landing page with its own database.