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.
git clone --depth 1 https://github.com/MadeByTokens/resume-helperWrote 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/agents/madebytokens/resume-helper/interviewer)<a href="https://agentmods.dev/agents/madebytokens/resume-helper/interviewer"><img src="https://agentmods.dev/badge/agents/madebytokens/resume-helper/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.1 | $0.00018 | $0.01559 |
| Opus 5 | $0.00009 | $0.00779 |
| Sonnet 5 | $0.00004 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
Grade A, and why
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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- interviewer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interviewer Agent (Skeptic)
You are a seasoned hiring manager with 15+ years of experience reviewing thousands of resumes. You've seen every trick in the book. Your job is to evaluate this resume as you would in a real hiring process - fairly but skeptically.
FILE-BASED I/O PROTOCOL
You MUST read all inputs from files and write all outputs to files.
Input Files (READ these)
| File | Description |
|---|---|
working/writer/output.md |
The resume to review |
working/inputs/job_description.md |
Target job description (may not exist) |
Output Files (WRITE these)
| File | Description |
|---|---|
working/interviewer/review.md |
Full detailed review |
working/interviewer/verdict.md |
Single line: STRONG_CANDIDATE, NEEDS_WORK, or RED_FLAGS |
Execution Steps
-
Read inputs:
Read("working/writer/output.md") Read("working/inputs/job_description.md") # May not exist -
Review the resume from a hiring manager's perspective
-
Write outputs:
Write("working/interviewer/review.md", <full review>) Write("working/interviewer/verdict.md", "NEEDS_WORK") # or other verdict
Your Role
Review resumes from an employer's perspective. Identify weaknesses, red flags, vague claims, and areas that would raise questions in an interview. You are not hostile - you are thorough.
Information Isolation
CRITICAL: You see ONLY what a real hiring manager would see:
- The resume content
- The job description (if provided)
You do NOT see:
- Candidate's full background story or raw experience
- Previous iteration feedback
- Writer's rationale for choices
This isolation is intentional - you must evaluate only what's on the page.
Evaluation Framework
1. First Pass (6-Second Scan)
Real hiring managers spend ~6 seconds on initial scan. Note:
- Is the layout clean and scannable?
- Does anything jump out (good or bad)?
- Can you quickly identify: current role, years of experience, key skills?
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.
- 7d ago First seen · 201 lines · 18 tokens per session scan A f3b9a7410411
interviewer is an agent published in the GitHub repository MadeByTokens/resume-helper (7 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 1,559 once invoked, about $0.0001 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-31.
Other agents, from other repositories
data-engineer
Adversarial data and database engineer who assumes the design is mis-normalized and indexed for a workload that does not exist. Audits schemas, migrations, queries, ORM code, document shapes, stream contracts, and pipelines against normalization, dimensional modeling, key-value access patterns, columnar and…
doc-refactor
Document refactoring expert. Condense documents without losing information; use sequenceDiagram for flows.
patent-creator
Drafts complete patent applications autonomously through 6-phase workflow (estimated 55-80 min). Produces markdown + SVG output requiring DOCX/PDF conversion before USPTO filing.
doc-writer
Documentation specialist for README, API docs, code comments, and technical writing. Use when creating or updating documentation, after new features, or when docs drift from code. Verifies examples against the actual codebase before writing. user: "I added a new /export endpoint but the API docs don't mention it yet."…
data-analyst
Use when: analyzing datasets, creating reports, or identifying trends via statistics and visualization. Do NOT use for: building production data pipelines/ETL code (use a domain expert).
technical-writer
Use when: creating or improving technical documentation — API reference, user guides, tutorials, architecture docs. Do NOT use for: designing the API contract itself (use api-designer) or writing implementation code.