setup

setup is a command for Claude Code from andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-. It costs 28 tokens per session (1,185 once invoked), scanned A, original, MIT.

A guided setup command for creating a job-search profile from a resume or answers to questions. The profile stores details such as work history, education, contact information, and target role.

In plain words
What is it for?
Use it to create or update a profile, extract information from a pasted resume, and prepare the details needed to evaluate jobs, tailor resumes, and write messages.
Why use it?
It gives later job-search tasks structured information about the person instead of making them repeat their background each time.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the career-ops-plugin-do-not-fork-currently-updating-v2- plugin — 10 skills, 2 commands, 1 agent shipped together

Good fit Use it to create or update a profile, extract information from a pasted resume, and prepare the details needed to evaluate jobs, tailor resumes, and write messages.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup
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.

Clone the repo
git clone --depth 1 https://github.com/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-

Made for: Claude Code.

Or install career-ops-plugin-do-not-fork-currently-updating-v2-, the plugin that ships this one along with the rest of its 10 skills, 2 commands, 1 agent.

Wrote 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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup/github.svg)](https://agentmods.dev/commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup)
Your own site
<a href="https://agentmods.dev/commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup"><img src="https://agentmods.dev/badge/commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup/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.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup"><img src="https://agentmods.dev/badge/commands/andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2-/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,185 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00028 $0.01185
Opus 5 $0.00014 $0.00593
Sonnet 5 $0.00006 $0.00237
Haiku 4.5 $0.00003 $0.00119

Measured 11d ago against content hash c184894dde6b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, 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 11d 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 · 140 lines

How it starts

The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set Up Your Profile

Walk the user through creating their job search profile. Conversational, friendly, zero jargon. This is the first thing a new user does.

Step 0: Check Existing

Read data/profile.yml. If it exists and no --reset flag:

"You're already set up! Here's a quick summary of your profile:

{Name} — {Current title} at {Company} Looking for: {Target role}

Want to update it? Say 'setup --reset' to start fresh, or tell me what to change and I'll update just that part."

If --reset flag or file doesn't exist, continue to Step 1.

Step 1: Welcome

"Let's set up your job search profile. This helps me evaluate jobs, tailor resumes, and write messages that actually sound like you.

Fastest way: Paste your resume below (text or PDF content) and I'll pull everything from it automatically.

Or I can ask you a few questions instead. What do you prefer?"

Step 2A: Resume Ingestion (preferred path)

If the user pastes resume content:

  1. Parse the resume into structured data:

    • Name, contact info, LinkedIn URL
    • Work history (each role: title, company, dates, bullet points)
    • Education (degree, school, year)
    • Skills (extract all mentioned skills and tools)
    • Certifications/licenses (if any)
    • Projects or portfolio items (if listed)
  2. Save the raw resume text to data/resume.md as a reference document.

  3. Ask follow-up questions for fields NOT in the resume:

    • "What kind of role are you looking for next?"
    • "Where are you willing to work? (Remote, specific city, flexible)"
    • "What's your target salary range? (Skip if you'd rather not say)"
    • "Anything else I should know? Career change, gap to explain, special situation?"
  4. Continue to Step 3.

Step 2B: Conversational Collection (fallback)

If the user prefers questions, ask these one at a time. Wait for each answer.

  1. "What's your name?"
  2. "What do you do right now? (Job title and company, or 'between jobs')"
  3. "Walk me through your last 2-3 roles briefly. For each: title, company, how long, and one or two things you accomplished."
  4. "What kind of role are you looking for? (Job title, industry)"
  5. "Where are you willing to work? (City, remote, hybrid, relocate)"
  6. "How many years of work experience total?"
  7. "What are your strongest skills? (Top 5-10)"
  8. "Any certifications or licenses? (Skip if none)"
  9. "What's your salary range? (Target and minimum, or skip)"
  10. "Got a LinkedIn profile URL?"
  11. "Anything else? (Career change, gap, special circumstances, portfolio)"

Read the full file on GitHub · 140 lines

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. 11d ago First seen · 140 lines · 28 tokens per session scan A c184894dde6b

Subscribe to this mod's changes

setup is a command published in the GitHub repository andrew-shwetzer/career-ops-plugin-do-not-fork-currently-updating-v2- (490 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 1,185 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-30.