job-seeker: Skill for Claude Code

.agents/skills/onboarding/SKILL.md

onboarding is a skill for Claude Code, Codex from galiprandi/job-seeker. It costs 21 tokens per session (1,913 once invoked), scanned A, original, MIT.

An initial setup routine for the browser, logins, database, user information, professional profile, and job-search strategy.

In plain words
What is it for?
It checks required software, configures browser visibility, stores preferences, and sets up the database and job-search data.
Why use it?
It prepares the information and access that the other job-search routines need before they can work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents); mentions AGENTS.md.

This is galiprandi/job-seeker's own configuration. It tells Claude Code and Codex how to work on job-seeker itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything job-seeker configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is node scripts/db.js "INSERT INTO preferences (user_id, category, key, value, confidence, source) VALUES (<user_id>, 'tooling', 'browser_mode', '<chosen_value>', .

Reuse

Borrowing it

Nothing to install: this file belongs to galiprandi/job-seeker. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/galiprandi/job-seeker/main/.agents/skills/onboarding/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/galiprandi/job-seeker

Made for: Claude Code, Codex.

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 onboarding

README.md
[![agentmods](https://agentmods.dev/badge/skills/galiprandi/job-seeker/onboarding/github.svg)](https://agentmods.dev/skills/galiprandi/job-seeker/onboarding)
Your own site
<a href="https://agentmods.dev/skills/galiprandi/job-seeker/onboarding"><img src="https://agentmods.dev/badge/skills/galiprandi/job-seeker/onboarding/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 onboarding

Your own site · 80×15
<a href="https://agentmods.dev/skills/galiprandi/job-seeker/onboarding"><img src="https://agentmods.dev/badge/skills/galiprandi/job-seeker/onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,913 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 94
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.00021 $0.01913
Opus 5 $0.00010 $0.00957
Sonnet 5 $0.00004 $0.00383
Haiku 4.5 $0.00002 $0.00191

Measured today against content hash cb5328df63d6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

onboarding 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 today.

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.

.agents/skills/onboarding/SKILL.md · 111 lines

How it starts

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

Onboarding

Steps

Phase 1: Technical setup

  1. Verify node and npx

  2. .gitignore: .browser-profile/, .playwright-cli/, .env, node_modules/

  3. npm init -y && npm install pg && npm install --save-dev @types/pg

  4. Ask user about browser visibility preference. Present these options and save the answer to preferences before opening any browser:

    • headless — Headless always. The agent works without showing the browser. Manual login/2FA remains headed (Gold Rule 5)
    • headed — Headed always. The user sees everything the agent does on screen
    • headed_logins_only — Headed only for logins/2FA, headless for everything else (default)
    • ask_each_time — The agent asks before each browser session whether the user wants to see it or not

    Save the preference:

    node scripts/db.js "INSERT INTO preferences (user_id, category, key, value, confidence, source) VALUES (<user_id>, 'tooling', 'browser_mode', '<chosen_value>', 1.0, 'explicit_statement') ON CONFLICT (user_id, category, key) DO UPDATE SET value = EXCLUDED.value, updated_at = NOW()" --write
    

    The agent must respect this preference in all flows that use the browser. Load it at every pre-flight:

    node scripts/db.js "SELECT value FROM preferences WHERE user_id = <user_id> AND category = 'tooling' AND key = 'browser_mode' AND status = 'active'"
    

    If no preference exists, default to headed_logins_only.

Phase 2: Browser and logins

  1. Open browser respecting the preference from step 4. For manual login it's always headed (Gold Rule 5). Use the wrapper (see AGENTS.md "Browser session"): node scripts/browser.js open <url> --headed
  2. Ask for email. Navigate to provider login (Gmail → accounts.google.com, Outlook → outlook.live.com). Fill email with fill, click Next, wait for manual auth + 2FA
  3. Validate session: navigate to inbox, confirm URL doesn't redirect to login

Phase 3: Database setup

  1. Database setup. Neon is the default recommended option. Present the options in this order:
    • Option A (recommended): Create a free DB on Neon. The agent navigates to console.neon.tech, logs in with Google (reuses session), creates a "New project", names it job-seeker, selects nearest region, and reads the connection string (Show password + eval to extract)
    • Option B: Bring your own connection string. If the user already has a Postgres DB (Neon, Supabase, Railway, local, etc.), they paste the connection string directly

Read the full file on GitHub · 111 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. today Changed cb5328df63d6
  2. 11d ago First seen · 111 lines · 21 tokens per session scan A 07a073833976

Subscribe to this mod's changes

onboarding is a skill published in the GitHub repository galiprandi/job-seeker (26 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,913 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.