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 ssmurfgg04-gif/context-m --skill interview-designergit clone --depth 1 https://github.com/ssmurfgg04-gif/context-mWrote 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/ssmurfgg04-gif/context-m/interview-designer)<a href="https://agentmods.dev/skills/ssmurfgg04-gif/context-m/interview-designer"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/interview-designer/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/ssmurfgg04-gif/context-m/interview-designer"><img src="https://agentmods.dev/badge/skills/ssmurfgg04-gif/context-m/interview-designer.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.00082 | $0.00850 |
| Opus 5 | $0.00041 | $0.00425 |
| Sonnet 5 | $0.00016 | $0.00170 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
interview-designer 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 6d 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 interview-designer — 0 lines 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Designer Skill
Core Mission: Elevate interview planning from "glancing at resume and asking questions" to "evidence-based investigation and projection." Operating Mechanism: Define Scorecard (set standards) → Forensic Scan (evidence gathering) → Future Simulation (performance prediction). Prompt Strategy: This skill uses <Chain of Thought>. When executing, maintain an "Objective Evaluator" perspective, seeking both Red Flags and Green Signals.
1. Dynamic War Room (Expert Panel)
Dynamically summon the most matching best minds into the war room based on candidate's role attributes:
- Geoff Smart (Who): Responsible for Define & Verify.
- Principle: Scorecard First. Before looking at any resume, clarify what the standard for an "A Player" is.
- Lou Adler (Performance-based): Responsible for Predict.
- Principle: Past performance predicts future performance only if the context is similar. Must design simulations for future scenarios.
- Daniel Kahneman (Bias Control): Responsible for De-bias.
- Principle: Beware of "confirmation bias." If concerns are found, also seek counter-evidence; if highlights are found, verify their replicability.
- Domain Expert: Responsible for Depth.
2. Core Execution Workflow
Step 1: Scorecard Definition - Smart's Priority
Don't look at the resume first! Based on JD or role requirements, define A Player standards for this position:
- Mission: One sentence - why does this role exist?
- Outcomes: 3-5 specific, measurable results that must be achieved within 12 months.
- Competencies: Hard/soft skills required to achieve the above outcomes.
Step 2: Forensic Resume Scan - Smart's Forensic
Use Step 1 standards to scan the resume, looking for Gaps (discrepancies) and High Points (highlights):
- The "Too Good To Be True" Heuristic: Logical gaps behind perfect data.
- The "Passenger vs Driver" Heuristic: Individual's true contributions under big company halo.
- The "First Principles" Heuristic: Principle understanding behind technical jargon.
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.
- 6d ago First seen · 54 lines · 82 tokens per session scan A 5505ed177082
interview-designer is a skill published in the GitHub repository ssmurfgg04-gif/context-m (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 82 tokens to every session and 850 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to interview-designer, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
test-plan
Build a test plan when a new Epic is created. Pulls epic details and linked stories from Jira, analyzes scope, and produces a test plan covering strategy, automation gap analysis, success criteria, environment needs, and risks. Output goes to Confluence and local test knowledge base. Use when: "test plan", "plan tests…
review-ticket
Review a Jira ticket during backlog grooming or refinement. Audits the ticket for testability, AC completeness, missing edge cases, and potential blockers. Outputs a structured review the SDT can bring to the grooming session. Use when: "review this ticket", "check ACs", "testability review", "grooming". Do NOT use…
setup
First-run configuration wizard for QABuddy. Sets up context source (Jira, spec docs, chat, custom), team mode (solo vs PR-based), and project preferences. Writes .qabuddy.json to the project root. Optionally wires QABuddy to run on pull requests (the reusable PR-coverage workflow). Re-run to reconfigure. Use when…
digest
NOTE: this skill requires connected chat / email / project-tracker / docs MCPs, which are typically only present in Cowork — the Code variant exists for parity but most users will want the Cowork variant. Cross-tool rollup of what's pending, what shipped, and what's blocked across chat / email / project tracker /…
backlog
View and manage pending backlog items. Use when user says '/backlog', '/backlog insights', '/backlog clear', 'what's pending', 'show backlogs', 'check backlog status'. (Code port — ADR-094.).
data_analysis
A data-analysis guide for doing mathematical calculations and descriptive statistics with confirmed, sourced data. Descriptive statistics summarise data using measures such as totals, averages, or ranges.