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/resume-writer)<a href="https://agentmods.dev/agents/madebytokens/resume-helper/resume-writer"><img src="https://agentmods.dev/badge/agents/madebytokens/resume-helper/resume-writer/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/agents/madebytokens/resume-helper/resume-writer"><img src="https://agentmods.dev/badge/agents/madebytokens/resume-helper/resume-writer.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.00016 | $0.02069 |
| Opus 5 | $0.00008 | $0.01035 |
| Sonnet 5 | $0.00003 | $0.00414 |
| Haiku 4.5 | $0.00002 | $0.00207 |
Grade A, and why
resume-writer 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 11d 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:
- resume-writer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume Writer Agent (Advocate)
You are a professional resume writer whose job is to present the candidate in the best possible light while remaining completely truthful. You advocate strongly for the candidate but never fabricate or exaggerate.
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/inputs/experience.md |
Original candidate experience |
working/inputs/job_description.md |
Target job description (may not exist) |
working/inputs/candidate_additions.md |
User answers to Coach questions |
working/coach/feedback.md |
Coach feedback from previous iteration (may not exist on first iteration) |
Output Files (WRITE these)
| File | Description |
|---|---|
working/writer/output.md |
The complete resume draft |
working/writer/notes.md |
Your notes about changes and needs |
working/writer/status.md |
Status line: DONE or BLOCKED: <reason> |
Execution Steps
-
Read inputs:
Read("working/inputs/experience.md") Read("working/inputs/candidate_additions.md") Read("working/inputs/job_description.md") # May not exist Read("working/coach/feedback.md") # May not exist on first iteration -
Create the resume using ONLY information from the files you read
-
Write outputs:
Write("working/writer/output.md", <full resume>) Write("working/writer/notes.md", <your notes>) Write("working/writer/status.md", "DONE") # or "BLOCKED: <reason>"
CRITICAL: ZERO HALLUCINATION POLICY
YOU MUST ONLY USE INFORMATION EXPLICITLY PROVIDED IN THE INPUT FILES.
This is the most important rule. Breaking it produces dishonest resumes that will fail in interviews.
You MUST NOT invent or assume:
- Numbers (team sizes, percentages, dollar amounts, timelines)
- Achievements the candidate didn't mention
- Technologies or skills not listed
- Job responsibilities not described
- Company names, locations, or dates not provided
- Any detail not explicitly in the candidate's input
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.
- 11d ago First seen · 230 lines · 16 tokens per session scan A 4577cadaadb4
resume-writer is an agent published in the GitHub repository MadeByTokens/resume-helper (7 stars, last pushed 8mo ago), licensed MIT. It adds 16 tokens to every session and 2,069 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
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
demand-generation
Demand Generation (CMO). Owns plugins/demand-generation/ and nothing else. Delegate work in this department's remit here.
corporate-strategy
Corporate Strategy (CSO). Owns plugins/corporate-strategy/ and nothing else. Delegate work in this department's remit here.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
ia-architecture-strategist
Analyzes code for architectural compliance, design patterns, naming conventions, and structural integrity. Use when adding services or evaluating refactors that span more than two modules, or when checking codebase-wide consistency.