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.
curl -O https://raw.githubusercontent.com/galiprandi/job-seeker/main/.agents/skills/onboarding/SKILL.mdgit clone --depth 1 https://github.com/galiprandi/job-seekerWrote 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.
[](https://agentmods.dev/skills/galiprandi/job-seeker/onboarding)<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.
<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>- NVIDIA SkillSpector warn
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.
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00021 | $0.01914 |
| Opus 5.5 | $0.00008 | $0.00766 |
| Sonnet 5.5 | $0.00004 | $0.00383 |
| Haiku 4.5 | $0.00002 | $0.00191 |
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 2d 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.
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
-
Verify
nodeandnpx -
.gitignore:.browser-profile/,.env,node_modules/ -
npm init -y && npm install pg && npm install --save-dev @types/pg -
Ask user about browser visibility preference. Present these options and save the answer to
preferencesbefore 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 screenheaded_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()" --writeThe 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
- 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 .agents/skills/browser-automation/scripts/browser.js open <url> --headed - 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 - Validate session: navigate to inbox, confirm URL doesn't redirect to login
Phase 3: Database setup
- 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
- 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
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.
- 2d ago Changed 44466e855646
- 1mo ago Changed cb5328df63d6
- 1mo ago First seen · 111 lines · 21 tokens per session scan A 07a073833976
onboarding is a skill published in the GitHub repository galiprandi/job-seeker (58 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 1,914 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
ai-dev-jobs-mcp
Search indexed AI and ML jobs, inspect listings and employers, match roles, and view salary and market stats via AI Dev Jobs MCP.
Cold Email Writer
Write personalized cold outreach emails to hiring managers and founders - specific, human, not a pitch deck.
resume-tailor
Use when the user has a specific job posting and wants to customize their resume, CV, work document, and/or cover letter for that role. Also use when they say "I'm applying to..." or share a job link.
vitaecontext-wiki-maintenance
Maintainer-only skill for refreshing VitaeContext wiki knowledge from official sources. Use only from a local repository clone when a maintainer asks to refresh one module, audit all module wiki entries, or audit module source lists.
resume-builder
Use when the user wants to create or update a source work document in resume or CV format, or create a source cover letter from scratch. Triggers on US resumes ("build my resume") and UK/EU-style work CVs ("build my CV", "I need a CV for a UK role", "European CV"). US academic CVs are out of scope. For first-time…
vitaecontext-vitaegraph
Build, deepen, validate, index, and maintain a private hierarchical career knowledge graph from supplied career materials. Use when the user asks to create or update a VitaeGraph, model education with nested courses or thesis work, enrich projects from Git repositories, or supply deep selected career context to…