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 instructions/leestott/interview-doctor-js/agents-mdgit clone --depth 1 https://github.com/leestott/interview-doctor-jsWrote 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/instructions/leestott/interview-doctor-js/agents-md)<a href="https://agentmods.dev/instructions/leestott/interview-doctor-js/agents-md"><img src="https://agentmods.dev/badge/instructions/leestott/interview-doctor-js/agents-md.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.01316 | $0.01316 |
| Opus 5 | $0.00658 | $0.00658 |
| Sonnet 5 | $0.00263 | $0.00263 |
| Haiku 4.5 | $0.00132 | $0.00132 |
Grade A, and why
interview-doctor-js AGENTS.md 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.
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.
Interview Doctor – Agent Instructions
Project Overview
Interview Doctor is an offline, AI-powered interview preparation assistant built with JavaScript, Foundry Local, and SQLite. It uses Retrieval-Augmented Generation (RAG) to generate tailored interview questions based on the user's CV/resume and job description.
Key constraint: This application runs 100% offline. Never introduce cloud dependencies, external API calls, or features that require internet connectivity.
Technology Stack
- Runtime: Node.js >= 20 (ES modules)
- AI: Foundry Local via
foundry-local-sdk– nativeChatClientfor inference (no OpenAI shim) - Database: SQLite via
sql.js– pure JavaScript, no native compilation (TF-IDF vectors for RAG retrieval) - PDF:
pdf-parsefor offline text extraction - Web: Express.js server + single-file HTML frontend (no build step, no framework)
- Tests: Node.js built-in test runner (
node:test+node:assert/strict)
Architecture
src/
├── config.js → Central configuration (model, paths, chunk sizes)
├── chunker.js → Text chunking + TF-IDF + cosine similarity
├── vectorStore.js → SQLite-backed vector store for RAG
├── pdfParser.js → PDF text extraction
├── chatEngine.js → RAG orchestration + Foundry Local LLM integration
├── prompts.js → System prompts (full + compact variants)
├── server.js → Express web server + REST/SSE API
└── ingest.js → Document ingestion script
Coding Conventions
- ES modules throughout (
import/export,"type": "module"in package.json) - No TypeScript — plain JavaScript for simplicity and zero build step
- Single-file frontend —
public/index.htmlcontains all HTML, CSS, and JS inline - No frameworks on the frontend — vanilla JavaScript, no React/Vue/etc.
- Parameterized queries for all SQLite operations (use
?placeholders with arrays, never string concatenation) - Async VectorStore — use
await VectorStore.create(dbPath)factory method (sql.js is async for init) - Path sanitization — all file operations validate paths stay within expected directories
- Error handling — Express routes catch and log errors, return appropriate HTTP status codes
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 · 125 lines · 1,316 tokens per session scan A 6b75e8a66648
interview-doctor-js AGENTS.md is an instructions file published in the GitHub repository leestott/interview-doctor-js (11 stars, last pushed 5mo ago), licensed MIT. It adds 1,316 tokens to every session, about $0.0066 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 instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.