AI-powered job search pipeline for Codex and OpenCode: evaluate roles, generate tailored CV PDFs, scan portals, apply to good-fit jobs, and track the whole search locally.
Paste a job URL. Get a scored evaluation, tailored CV, and tracker entry.
Most users should scaffold a personal job-search project instead of cloning this harness repo directly.
- Codex or OpenCode installed and configured
- Node.js 20.6 or newer
- Optional: Go, only if you want to build the dashboard TUI
npx --package=job-forge create-job-forge my-job-search
cd my-job-search
npm installThen edit the three personal files the scaffolder creates:
| File | What to put there |
|---|---|
cv.md |
Your CV in markdown. This is the source for matching and PDF generation. |
config/profile.yml |
Your identity, target roles, US work eligibility and location constraints, compensation, and proof points. |
portals.yml |
Companies, search queries, title filters, and US coverage policy for portal scanning. |
Optional: add article-digest.md with portfolio links, case studies, or extra proof points.
npx job-forge sync-check
codex # or: opencodeInside Codex or OpenCode, paste a job URL or job description. JobForge routes it through the auto-pipeline: evaluation, score, tailored report, PDF, and tracker update.
To see the command menu:
Use $job-forge in Codex or /job-forge in OpenCode to see the command menu.
JobForge is built for selective, high-fit applications. It is not intended for spray-and-pray submission.
- Scores opportunities with a consistent weighted rubric.
- Generates tailored ATS-friendly CV PDFs.
- Scans configured company portals and job boards, restricting discovery to postings that explicitly permit work in the United States.
- Balances eligible results across Northeast, Midwest, South, West, and nationwide/US-remote buckets while limiting per-company concentration.
- Blocks automatic outreach, form filling, and submission when US eligibility is ambiguous or absent.
- Tracks applications, follow-ups, rejections, offers, reports, and PDFs.
- Supports batch evaluation and application work through bounded subagents.
- Uses local helper CLIs for dedupe, scoring, lineage, preflight, postflight, receipts, and tracker integrity.
Run these from your personal project root after npm install.
| Need | Command |
|---|---|
| Verify setup after editing profile and CV | npx job-forge sync-check |
| Check tracker and pipeline health | npx job-forge verify |
| Merge batch tracker additions | npx job-forge merge |
| Generate a CV PDF from the current project | npx job-forge pdf |
| Show token usage | npx job-forge tokens --days 1 |
| Create a verifiable evidence receipt | npx job-forge receipts:create --artifact <file> |
| Rebuild harness symlinks | npx job-forge sync |
| Upgrade the harness | npm run update-harness |
Useful agent commands:
| Need | Codex | OpenCode |
|---|---|---|
| Evaluate a pasted URL or JD | Paste it directly, or use $job-forge |
Paste it directly, or use /job-forge |
| Scan configured portals | $job-forge scan |
/job-forge scan |
| Process queued URLs | $job-forge pipeline |
/job-forge pipeline |
| Batch evaluate roles | $job-forge batch |
/job-forge batch |
| Fill an application form | $job-forge apply |
/job-forge apply |
| Check application status | $job-forge tracker |
/job-forge tracker |
| Check due follow-ups | $job-forge followup |
/job-forge followup |
| Draft LinkedIn outreach | $job-forge contact |
/job-forge contact |
| Research a company | $job-forge deep |
/job-forge deep |
| Handle rejection or offer workflows | $job-forge rejection or $job-forge negotiation |
/job-forge rejection or /job-forge negotiation |
Paste a job URL or JD
|
v
Extract role details and classify fit
|
v
Score against profile, CV, location, comp, and role goals
|
v
Create report + tailored PDF + tracker entry
|
v
Apply, follow up, research, or negotiate from the tracked state
A scaffolded personal project looks like this:
my-job-search/
├── package.json # depends on job-forge from npm
├── opencode.json # MCP and opencode configuration
├── cv.md # personal, gitignored
├── article-digest.md # optional personal proof points, gitignored
├── config/profile.yml # personal, gitignored
├── portals.yml # personal scanner config, gitignored
├── data/ # pipeline, applications, scan history
├── reports/ # generated evaluations
├── output/ # generated PDFs
├── batch/tracker-additions/ # batch apply/eval results before merge
├── AGENTS.md # personal overrides
├── AGENTS.harness.md # symlink into node_modules/job-forge
├── .agents/skills/job-forge/ # shared Codex + OpenCode skill
├── .codex/config.toml # Codex MCP and model configuration
├── .opencode/commands/job-forge.md # OpenCode /job-forge command
├── .opencode/skills/job-forge.md # compatibility for older OpenCode releases
├── modes/ # symlinked JobForge modes
├── templates/ # symlinked policies and templates
└── node_modules/job-forge/ # the harness package
Your personal files and generated job-search state are gitignored by the scaffolded project.
The scaffolded project wires up the browser and mail automation JobForge needs for Codex and OpenCode:
- Geometra MCP for browser automation and PDF generation.
- Gmail MCP for recruiter replies, interview callbacks, offer responses, and status emails.
The harness also ships config for Cursor and Claude Code through generated symlinks. npm install and npx job-forge sync refresh every client link.
Clone this repo directly only when you want to work on the harness itself: modes, scripts, templates, generated agent configs, or release packaging.
git clone https://github.com/Agent-Pattern-Labs/JobForge.git
cd JobForge
npm install
npm run build:config
npm run verifyThe source of truth for generated harness configuration and the shared JobForge skill is under iso/. Run npm run build:config after changing iso/ files.
- Setup - full install paths, personalization, tracker setup, token tracking, troubleshooting.
- Architecture - consumer vs harness split, modes, scripts, batch flow, generated config.
- Customization - profile, archetypes, scanner keywords, states, templates, local overrides.
- Model Routing - subagent tiers and how to change model routing.
- Examples - fictional CVs, sample JD, and sample report.
- Batch Runner - TSV format, durable batch runner, merge flow.
- Contributing - branch workflow and quality checks.
sync-check fails before your CV/profile are complete. That is expected until cv.md and config/profile.yml are filled in.
If symlinks look stale after moving a project, run:
npx job-forge syncIf PDF or browser automation fails, start with:
opencode mcp listThen see docs/SETUP.md for Geometra, Gmail, dashboard, tracker, and merge troubleshooting.
MIT