setup

A setup command for creating a job-search workspace and connecting job-search services using your own account keys. The workspace stores your profile, imported files, job tracker, and supporting folders.

In plain words
What is it for?
Use it to create or locate a workspace, build its initial files, check connector status, and connect services such as Indeed, Adzuna, Firecrawl, Reed, or Dice.
Why use it?
It gives the job-search tools a consistent place to store information and shows which connections are ready or missing. Optional keys do not have to be configured before the profile can be built.

Command

Part of the jobxhunter plugin — 1 skill, 8 commands, 2 agents, 3 MCP servers shipped together

Install

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.

agentmods
npx agentmods add commands/soheilfallah/jobxhunter/setup
Clone the repo
git clone --depth 1 https://github.com/soheilfallah/jobxhunter

Or install jobxhunter, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 2 agents, 3 MCP servers.

Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 414 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00414
Opus 5 $0.00010 $0.00207
Sonnet 5 $0.00004 $0.00083
Haiku 4.5 $0.00002 $0.00041

Measured 3d ago against content hash 3c5423c39a88, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup 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 3d 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.

commands/setup.md · 26 lines

What it actually says

Use the jobxhunter skill's SETUP routine.

Walk the user through SETUP.md, one step at a time, and verify each step before the next. Keys are step 5 and optional — never lead with them, never block on them. Stop after the profile is built and the user has looked at it; tell them which command to run next.

  1. Resolve or create the workspace (python "${CLAUDE_PLUGIN_ROOT}/scripts/_lib.py" resolve; if none, scaffold with python "${CLAUDE_PLUGIN_ROOT}/scripts/init_workspace.py" --workspace <dir> [--name <who>]). This drops the profile template, the dump/ folder, WORKSPACE-MAP.md, and the tracker, then stops.
  2. Onboard the connectors (only after the profile exists and the user said "now"): run python "${CLAUDE_PLUGIN_ROOT}/scripts/setup_connectors.py" doctor for a report of what's set vs missing, then follow the Agent script in references/tools-and-connectors.md for each missing one, in its order: Indeed first (built into claude.ai — Settings → Connectors → Indeed → Connect, no key), then Adzuna, Firecrawl, Reed, Dice optional. One connector per message; never block on a key; say what still works without it. Keys are the plugin's user-config values (/plugin configure or claude plugin install … --config KEY=VALUE) — no manual JSON editing. Re-run the doctor after the user restarts Claude Code.

Follow SKILL.md ("Command: SETUP") and references/tools-and-connectors.md. Stop after setup so nothing runs against an empty profile.

Changes

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.

  1. 3d ago First seen · 26 lines · 20 tokens per session scan A 3c5423c39a88

Subscribe to this mod's changes

setup is a command published in the GitHub repository soheilfallah/jobxhunter (8 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 414 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.