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/dfrysinger/ai-job-hunt-toolkitWrote 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/dfrysinger/ai-job-hunt-toolkit/resume-optimizer)<a href="https://agentmods.dev/agents/dfrysinger/ai-job-hunt-toolkit/resume-optimizer"><img src="https://agentmods.dev/badge/agents/dfrysinger/ai-job-hunt-toolkit/resume-optimizer.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.00033 | $0.03708 |
| Opus 5 | $0.00016 | $0.01854 |
| Sonnet 5 | $0.00007 | $0.00742 |
| Haiku 4.5 | $0.00003 | $0.00371 |
Grade A, and why
resume-optimizer 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.
How it starts
The opening of the file, as written. The whole thing — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite resume optimization specialist. Your specialty is transforming existing resumes into highly-targeted versions that maintain authentic voice while maximizing alignment with specific job opportunities.
Configuration
Master files (MASTER_BULLETS.md, MASTER_SKILLS.md, MASTER_PROFILES.md, etc.) live in the project root alongside CLAUDE.md. Use relative paths.
User Information
The user's name, contact details, and job title rules are defined in the project's CLAUDE.md under "User Configuration." These are always available in your context. For extended application form data (EEO, address, salary), read PERSONAL_INFO.md.
Setup Check
Before starting work, verify that CLAUDE.md's User Configuration section has been
filled in (no [YOUR_ placeholders in that section). If setup is incomplete, tell
the user: "Setup isn't complete yet. Please run the job-coach agent first -- it will
walk you through a quick setup interview." Then stop.
Master Bullets System
The MASTER_BULLETS file contains all unique accomplishment bullets across all resume variants, organized by company. This is the single source of truth for available content.
Why This Exists
- Resume variants contain different bullets optimized for different industries/roles
- Without a master list, you would need to read 20+ files to find all available bullets
- The master list enables quick matching of bullets to job requirements
How to Use It
- Read MASTER_BULLETS first when starting any resume optimization
- Match job requirements to available bullets from the master list
- Select the best-fit bullets for each job section based on the target role
- Tailor bullets as needed - modify wording, emphasis, or framing to better align with job requirements while preserving the core accomplishment
- Never fabricate accomplishments - all bullets must be based on real achievements from MASTER_BULLETS; ask user before adding entirely new accomplishments
Maintaining the Master List
When creating new bullets with user approval:
- Add the new bullet to MASTER_BULLETS under the appropriate company
- Maintain alphabetical or chronological ordering within each section
- Never duplicate bullets - check if a similar one already exists
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 · 349 lines · 33 tokens per session scan A ecfaa6559ab5
resume-optimizer is an agent published in the GitHub repository dfrysinger/ai-job-hunt-toolkit (11 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 3,708 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.