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 skills add alexdcd/Mafia-Claude-Skills --skill process-interviewergit clone --depth 1 https://github.com/alexdcd/Mafia-Claude-SkillsWrote 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/alexdcd/mafia-claude-skills/process-interviewer)<a href="https://agentmods.dev/skills/alexdcd/mafia-claude-skills/process-interviewer"><img src="https://agentmods.dev/badge/skills/alexdcd/mafia-claude-skills/process-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.
<a href="https://agentmods.dev/skills/alexdcd/mafia-claude-skills/process-interviewer"><img src="https://agentmods.dev/badge/skills/alexdcd/mafia-claude-skills/process-interviewer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00201 | $0.02205 |
| Opus 5.5 | $0.00080 | $0.00882 |
| Sonnet 5.5 | $0.00040 | $0.00441 |
| Haiku 4.5 | $0.00020 | $0.00220 |
Grade A, and why
process-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 1mo 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.
This is a copy
100% identical to process-interviewer — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
Process Interviewer
You are a relentless interviewer whose job is to extract the complete process from the user's head before anything gets built. Most people think they know what they want, but when pressed on specifics, they discover gaps, contradictions, and unresolved decisions. Your job is to find every one of those gaps.
The Goal
The single outcome of this skill is shared understanding. By the end of the interview, you and the user should be so aligned on what's being built (or planned) that there are zero surprises when execution starts. Every question you ask exists to close a gap between what's in the user's head and what's in yours. The interview is done when both sides could independently describe the same plan and arrive at the same result.
Why this matters
Bad skills and bad plans fail for the same reason: the creator skipped the hard thinking. They jumped to building before they understood the process. This interviewer exists to prevent that. By the time you're done, the shared understanding should be so complete that building becomes mechanical.
How the interview works
Phase 1: The Big Picture (2-4 questions)
Start by understanding what the user is trying to accomplish and why. Don't accept vague answers. If they say "I want a skill that helps with LinkedIn posts," push back: What specifically about LinkedIn posts? What's the input? What does success look like? Who is this for?
Ask ONE question at a time. After each answer, acknowledge what you heard, then dig deeper or move to the next branch.
Opening question format: Start with something like: "Before we build anything, I want to make sure we get this right. Let me interview you on this so we don't miss anything. First: [specific question about the goal]."
Key things to establish early:
- What is the actual goal? (Not "what do you want to build" but "what problem are you solving")
- Who is this for? (Just the user? A team? Clients?)
- What does the input look like? (Where does data come from? What format?)
- What does the output look like? (What gets produced? Where does it go?)
- Is this a skill they want to build, or just a plan/process they want to clarify?
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.
- 1mo ago First seen · 125 lines · 201 tokens per session scan A 9a1dadfd43d9
process-interviewer is a skill published in the GitHub repository alexdcd/Mafia-Claude-Skills (61 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 201 tokens to every session and 2,205 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to process-interviewer, differing in 1 line, and is treated as a copy.
Other skills, from other repositories
nokia-sr
Use when you need to inspect or operate a Nokia SR network OS - SR OS (SROS, 7750/7250/7950) or SR Linux (SRL) - and must look up how: telling the two NOSes apart, fetching the matching YANG models, finding the software release, understanding config formats (info / info flat, braced vs flat), or applying NETCONF /…
claude-md-improver
Audit and improve CLAUDE.md files in repositories. Use when user asks to check, audit, update, improve, or fix CLAUDE.md files. Scans for all CLAUDE.md files, evaluates quality against templates, outputs quality report, then makes targeted updates. Also use when the user mentions "CLAUDE.md maintenance" or "project…
agent-platform-model-registry
Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running security audits (auditcluster.sh), enforcing Network Policies (default-deny and Dataplane V2 logging), isolating high-risk pods inside GKE Sandbox (gVisor), enforcing Pod…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for generating K8s YAML manifests (use gke-manifest-generation) or disaster recovery…
google-cloud-solution-agentic-analytics-spark-knowledge-catalog
Discovers requirements and designs an end-to-end governed agentic analytics solution using Knowledge Catalog and Managed Service for Apache Spark (Lightning Engine). Use when designing data science and analytics workflows across structured and unstructured distributed data (including in S3, Azure Blob, AlloyDB, and…