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 skills/suxrobgm/jobpilot/auto-applynpx skills add suxrobGM/jobpilot --skill auto-applygit clone --depth 1 https://github.com/suxrobGM/jobpilotWhat 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.00034 | $0.02957 |
| Opus 5 | $0.00017 | $0.01478 |
| Sonnet 5 | $0.00007 | $0.00591 |
| Haiku 4.5 | $0.00003 | $0.00296 |
Grade A, and why
auto-apply scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS -H "authorization: Bearer $JOBPILOT_API_TOKEN" "$JOBPILOT_API/api/campaigns?status=in_progress" How it starts
The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto-apply - Search + Apply On Demand
Keep the chosen board open in tab 1; for each result that qualifies, delegate the application to the job-worker subagent (it works in its own tab and returns a compact result), then move to the next job. No batch pre-discovery and no per-job approval - launching the campaign is the confirmation. Pause only for 2FA / payment. A CAPTCHA is not a pause - attempt the solve-captcha skill; if unsolved, skip the job (never pause) and the user finishes it later via the apply skill. Live view at $JOBPILOT_WEB/campaigns/<campaign-id>.
Setup
Follow ../_shared/setup.md. Shared campaign mechanics (applied-check, result writes, worker
input, rules) live in ../_shared/campaign-flow.md. Read autoApply (defaults applied per field):
| Setting | Default | Notes |
|---|---|---|
minMatchScore |
60 | Qualification threshold (0-100). Inline --min-score overrides. |
maxApplicationsPerCampaign |
null (unlimited) |
Stop after this many successful applies. Inline --max-apps overrides; omit → unlimited. |
defaultStartDate |
"2 weeks notice" |
Default start-date answer. |
Inline argument overrides take precedence. --board <domain> is required unless the argument is resume or retry-failed <campaign-id>.
Campaign Modes
"resume"→ list incomplete campaigns (GET /api/campaigns?status=in_progress), ask which to resume, replay the apply loop on remainingapplying/approved/pendingjobs."retry-failed <campaign-id>"→ fetch the campaign; for every retryablefailedjob, POST its/retrycommand with the currentretryNotes, then replay the apply loop on those approved rows.- Otherwise → search query → Phase 0.
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.
- yesterday First seen · 177 lines · 34 tokens per session scan A 5547e84237b9
auto-apply is a skill published in the GitHub repository suxrobGM/jobpilot (60 stars, last pushed 11d ago), licensed MIT. It adds 34 tokens to every session and 2,957 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
scrape
Finds new job postings matching your profile via installed portal-search CLIs (job-board APIs and any skills added with /add-portal). Deduplicates across runs. Triggers on: job scrape, find jobs, search jobs, new jobs, job search, scrape jobs, /scrape.
scrape
Finds new job postings matching your profile via installed portal-search CLIs (LinkedIn, local job boards, and any skills added with /add-portal). Deduplicates across runs. Triggers on: job scrape, find jobs, search jobs, new jobs, job search, scrape jobs, /scrape.
job-application-agent
Finds, evaluates, fills, submits, and tracks a candidate's own job applications using a verified resume, evidence-based targeting, secure local profile storage, and browser automation. Use for onboarding or migrating a job-search profile, searching active roles, assessing a posting, applying to an authorized URL or…
job-apply
Fill out job applications automatically using your resume. Use when the user wants to apply for jobs on LinkedIn Easy Apply, Greenhouse, Ashby, Lever, Rippling, or Workday.
answer-memory
Manage Job Apply's local profile, reusable answers, application history, and resumable sessions. Use whenever a Job Apply workflow needs to initialize, migrate, read, or update persistent applicant data.
job-search
Search LinkedIn, Hacker News, and Twitter/X for jobs with connections, hiring manager insights, and preference-based scoring. Use when the user wants to find jobs, search for positions, or explore job opportunities.