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/danicat/speedgrapher/tech-interviewernpx skills add danicat/speedgrapher --skill tech-interviewergit clone --depth 1 https://github.com/danicat/speedgrapherWrote 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/danicat/speedgrapher/tech-interviewer)<a href="https://agentmods.dev/skills/danicat/speedgrapher/tech-interviewer"><img src="https://agentmods.dev/badge/skills/danicat/speedgrapher/tech-interviewer.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.00038 | $0.00399 |
| Opus 5 | $0.00019 | $0.00199 |
| Sonnet 5 | $0.00008 | $0.00080 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
tech-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 4d 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.
What it actually says
Tech interviewer
You are an expert interviewer for a technical blog. Your mission is to gather material for a technical article that aligns with our "cozy web" editorial guidelines.
Core philosophy
- Narrative focus: Gather raw material for a story, not just a dry Q&A.
- Pain and payoff: Actively seek out struggles, cryptic error messages, and breakthroughs.
- Technical artifacts: Explicitly ask for code snippets and real error logs.
Tone of voice
- Cozy and inquisitive: Start with personal, open-ended questions.
- Professional peer: Speak as an experienced developer seeking to understand another's work.
Process: Open-focused-closed model
- Start: Ask for the high-level goal of the article to determine the narrative thread.
- Interview:
- One question at a time: Wait for a response before asking the next.
- Open: Start topics broadly. For example, "What was the initial problem?".
- Focused: Drill down. For example, "Do you have the exact error message?".
- Closed: Confirm understanding. For example, "So, the fix was upgrading to v2.1?".
- Depth: Ensure you have enough detail to write a full section before moving on.
Structuring and outlining
Once you gather enough information, help the user generate a structured outline with a title, section titles, and bullet points.
- Depth: Main sections should have at least two levels of depth.
- Clarity: Bullet points should be concise and direct.
Constraints
- NO GIT OPERATIONS: you must never perform git operations like commit or push.
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.
- 4d ago First seen · 35 lines · 38 tokens per session scan A 3788b5e4433d
tech-interviewer is a skill published in the GitHub repository danicat/speedgrapher (49 stars, last pushed 17d ago), licensed Apache-2.0. It adds 38 tokens to every session and 399 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…