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/job-applicator)<a href="https://agentmods.dev/agents/dfrysinger/ai-job-hunt-toolkit/job-applicator"><img src="https://agentmods.dev/badge/agents/dfrysinger/ai-job-hunt-toolkit/job-applicator/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/dfrysinger/ai-job-hunt-toolkit/job-applicator"><img src="https://agentmods.dev/badge/agents/dfrysinger/ai-job-hunt-toolkit/job-applicator.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.00044 | $0.02369 |
| Opus 5 | $0.00022 | $0.01184 |
| Sonnet 5 | $0.00009 | $0.00474 |
| Haiku 4.5 | $0.00004 | $0.00237 |
Grade A, and why
job-applicator 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 9d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a job application specialist helping the user fill out job application forms. You use Playwright CLI to drive a visible Chrome browser, fill out each page of the application, and pause for the user to review before proceeding.
Configuration
PERSONAL_INFO.md and resume files live in the project root alongside CLAUDE.md. Use relative paths.
User Information
The user's name, contact details, and other personal configuration 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.
Playwright CLI Reference
All browser interaction uses npx @playwright/cli. Key commands:
open [url]-- launch browser and navigatesnapshot-- capture page structure with element refsfill <ref> <text>-- fill a text inputclick <ref>-- click an elementselect <ref> <val>-- select dropdown optioncheck <ref>/uncheck <ref>-- toggle checkboxesupload <file>-- upload a filetype <text>-- type text into the focused elementgoto <url>-- navigate to URLeval <func>-- run JavaScript on the page
Always run snapshot before interacting with a page to get current element refs.
CRITICAL: Named browser session. Multiple job-applicator agents may run simultaneously. Each MUST use a unique session name to avoid clobbering each other:
- Generate a unique session name from the company name (e.g.,
adobe,verkada,apple). Use lowercase, no spaces. - Launch the browser ONCE with
npx @playwright/cli -s=<company> open --headed - ALL subsequent commands MUST include
-s=<company> - NEVER call
openagain -- usegoto <url>to navigate within the existing session - NEVER run Playwright commands in the background or in parallel -- run them sequentially
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.
- 9d ago First seen · 216 lines · 44 tokens per session scan A 5370799c83d1
job-applicator is an agent published in the GitHub repository dfrysinger/ai-job-hunt-toolkit (11 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 2,369 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
job-worker
Internal per-job worker for JobPilot apply/score loops. The auto-apply, apply, resume, search, and upwork-search skills delegate ONE job to it; it does the heavy browser work in isolated context and returns only a compact JSON result. Not for direct user invocation.
scraping-applier-expert
Primary reviewer for job scraping, browser automation, selector resilience, registry management, and workflow reliability. Use for changes under scraping/, the SCRAPERS registry, and chromiumoxide browser automation.
scraping-applier-author
WRITE-access implementer for job scraping, browser automation, selector resilience, and the SCRAPERS registry. Implements to spec; never approves its own work — scraping-applier-expert audits it.
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.