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/mishahanin/heading-os/interview-prepnpx skills add mishahanin/heading-os --skill interview-prepgit clone --depth 1 https://github.com/mishahanin/heading-osWrote 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/mishahanin/heading-os/interview-prep)<a href="https://agentmods.dev/skills/mishahanin/heading-os/interview-prep"><img src="https://agentmods.dev/badge/skills/mishahanin/heading-os/interview-prep.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.00089 | $0.01165 |
| Opus 5 | $0.00044 | $0.00583 |
| Sonnet 5 | $0.00018 | $0.00233 |
| Haiku 4.5 | $0.00009 | $0.00117 |
Grade A, and why
interview-prep 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 5d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Prep
Produce an interview framework with position-specific questions and scoring rubric.
Variables
position: [Job title and department]
level: junior | mid | senior | leadership
context: [What specifically this role needs to do; any team or project context]
candidate: [Candidate name, background summary if pre-interview — optional]
Instructions
Before drafting, read:
context/business-info.md— 31C company, Tribe culture, hiring standard (1,500+ interviews for ~20 hires)reference/billion-growth-playbook.md— Section 9: Scaling the Tribe (hiring philosophy, culture carriers)outputs/operations/workspace/31c-operational-state-model.md— Five Core Principles (what we're screening for behaviorally)reference/misha-voice.md— The voice of 31C (screen for culture fit)
The 31C Hiring Standard
The bar never drops. Every hire is a culture carrier. We've done 1,500+ interviews for ~20 hires. What we're looking for:
- Evidence of delivery under pressure (not intent — proof)
- Intellectual honesty (can they say they were wrong?)
- Alignment with Data Sovereignty (do they understand why it matters?)
- Partnership orientation (do they build relationships or execute transactions?)
- Navigation instinct (do they adapt or freeze when conditions change?)
Phase 1: Role-Specific Question Bank (20 questions)
Opening questions (warm-up, 2-3): [Calibrated to position and level — make them feel like a conversation, not an interrogation]
Technical/functional questions (8-10): [Role-specific; drawn from the position requirements — depth over breadth]
Behavioral questions — Five Core Principles (5):
- Proof of Value: "Tell me about a time you killed a project because it wasn't creating real value."
- Partnership for Life: "Describe a relationship you maintained even when it was difficult."
- Integrity: "Tell me about a time you delivered bad news to a superior. What happened?"
- Deliver Under Pressure: "What's the hardest operational situation you've been in? What did you do?"
- Data Sovereignty: "How do you think about data privacy and client trust in your work?"
What ships with it
1 file 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.
- 5d ago First seen · 133 lines · 89 tokens per session scan A 8d8a9611d5d5
interview-prep is a skill published in the GitHub repository mishahanin/heading-os (11 stars, last pushed today), licensed Apache-2.0. It adds 89 tokens to every session and 1,165 once invoked, about $0.0004 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
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
duckduckgo-search
Free keyless web, news, and image search via ddgs.
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.