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 scott-fryxell/brayness --skill interview-prepgit clone --depth 1 https://github.com/scott-fryxell/braynessWrote 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/scott-fryxell/brayness/interview-prep)<a href="https://agentmods.dev/skills/scott-fryxell/brayness/interview-prep"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/interview-prep/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/scott-fryxell/brayness/interview-prep"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/interview-prep.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.00118 | $0.00824 |
| Opus 5.5 | $0.00047 | $0.00330 |
| Sonnet 5.5 | $0.00024 | $0.00165 |
| Haiku 4.5 | $0.00012 | $0.00082 |
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 28d 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interview Prep
Prepares a target company/role end-to-end: research, fit, behavioral prep, technical prep, and process tracking. All notes live in the vault under 02 Areas/Job Hunt/ (work/vault/02 Areas/Job Hunt/) -- see references/process-and-tracker.md for the exact layout.
Workflow
-
Capture the target. Get company name, role, and how it came up (referral, job post, cold interest). Create
02 Areas/Job Hunt/Companies/<company-slug>.mdfromassets/company-note-template.mdif it doesn't exist. Add a row to02 Areas/Job Hunt/tracker.md. -
Research the company. Read
references/research.md. Use WebSearch/WebFetch to fill in product, stage, recent news, tech stack, competitors, culture signals. Write findings into the company note. -
Explore the fit. Read
references/fit-and-story-bank.md. Work through why this is actually interesting (not generic enthusiasm), cross-check the vault for existing related interests, and draft 2-3 tailored questions to ask interviewers. -
Prep for the format. Determine what rounds are coming (or likely, from research/role type):
- Behavioral round ->
references/fit-and-story-bank.mdSTAR story bank. - Technical/DSA round ->
references/technical-prep.md, includingwork/kata-machinefor hands-on practice. - System design or take-home -> same file, relevant section.
- Behavioral round ->
-
Track through the process. Read
references/process-and-tracker.md. Updatetracker.mdand the company note's hiring-process table as stages happen. Log post-interview notes right after each round while it's fresh. -
Offer stage. When an offer lands, use the negotiation section of
references/process-and-tracker.mdbefore any number gets discussed live.
Baselining
An interview is a shared baseline before it is a performance. Scott's pattern: answer one part of a question, get to a shared footing on that part, then answer the rest from there. Advancing to the next question before the floor is set reads as noise, not rigor.
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.
- 28d ago Changed · +16 lines 062c6bd9ee65
- 1mo ago First seen · 32 lines · 118 tokens per session scan A 3a5449940b92
interview-prep is a skill published in the GitHub repository scott-fryxell/brayness (125 stars, last pushed 29d ago), licensed MIT. It adds 118 tokens to every session and 824 once invoked, about $0.0005 per session on Opus 5.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
hr-onboarding
A new-hire onboarding plan as a single page — first week schedule, buddy + manager intro, learning track, equipment checklist, and "you're set when…" outcomes. Use when the brief mentions "onboarding", "new hire", "first week plan", or "入职".
book-mirror
Take any book (EPUB/PDF), produce a personalized chapter-by-chapter analysis. Each chapter is preserved in detail (The Chapter) and mirrored back to the reader's actual life (The Mirror) using brain context. The mirror observes and resonates — a friend pointing out parallels, NOT a consultant rearranging the reader's…
lean-formalize
Develop and verify a mathematical proof in Lean, continue an incomplete Lean project, or audit whether it proves the original statement. Connect actual inputs to intermediate lemmas, assemble the target theorem, check its transitive axioms, and provide a reproducible handoff. Use when Lean is requested or a specific…
exam-forecast
Analyze past exams from the same professor to surface patterns — subject weighting, recurring issue-spot traps, favored hypo types, policy-vs-doctrine mix — and forecast likely emphases for the upcoming exam. Use when the user says "what's on the exam", "analyze past exams", "predict the exam", or shares past exams.
eli5
Explain research, papers, or technical ideas in plain English with minimal jargon, concrete analogies, and clear takeaways. Use when the user says "ELI5 this", asks for a simple explanation of a paper or research result, wants jargon removed, or asks what something technically dense actually means.
deck-course-module
A course or workshop slide template with persistent learning goals, teaching pages, multiple-choice self-tests, and a wrap-up.