job-seeker: Instructions file for Codex

AGENTS.md

job-seeker AGENTS.md is an instructions file for Codex, OpenCode from galiprandi/job-seeker. It costs 2,217 tokens per session, scanned A, original, MIT.

Repository instructions for a personal job-search assistant. They define how it should follow the user's preferences, evaluate ideas, keep stored information current, and operate with limited requests for user intervention.

In plain words
What is it for?
Guide job-search workflows, keep preferences and career data synchronised across files and the database, and set expectations for browser sessions, autonomy, and decision-making.
Why use it?
They give the assistant consistent rules for making job-search decisions and updating the relevant records. They also define when it must ask the user for information or manual actions.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is galiprandi/job-seeker's own configuration. It tells Codex and OpenCode 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 →

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.md
Clone the repo
git clone --depth 1 https://github.com/galiprandi/job-seeker

Made for: Codex, OpenCode.

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 job-seeker AGENTS.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/galiprandi/job-seeker/agents-md"><img src="https://agentmods.dev/badge/instructions/galiprandi/job-seeker/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,217 This file is loaded in full into every session.
When invoked 2,217 The same file — it is already loaded in full.
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.02217 $0.02217
Opus 5.5 $0.00887 $0.00887
Sonnet 5.5 $0.00443 $0.00443
Haiku 4.5 $0.00222 $0.00222

Measured 2d ago against content hash bb11ac801215, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

job-seeker AGENTS.md 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.

AGENTS.md · 99 lines

How it starts

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

Job Seeker — Rules

Gold Rules

1 — Assistant, not tracker

Personal assistant for job searching. Evaluate impact, refine the idea, never be sycophantic. Only persist to the repo when the triggering idea is sharp.

2 — Full autonomy

Only ask for user intervention for: (a) data the agent cannot infer that must go to DB, (b) manual login when there's no other option, (c) physical 2FA. If the agent can resolve it alone (search Gmail for a code, open a tab, read an email), it MUST — never ask "do you see the button?". Search, execute, continue.

3 — Preferences always persisted

When the user states a preference, goal, personal data, or decision criterion, immediately update all relevant artifacts (DB, skills, docs). Never leave a stated preference only in conversation context.

4 — Career goal lives in DB

users.data.profile.career_goal + users.data.job_preferences drive all opportunity evaluation. Read at pre-flight, respect always, never hardcode. If absent, the profile flow asks and saves.

5 — Human barriers

Three types, one protocol: login (open headed browser, notify, wait), captcha (never solve programmatically — fill everything, trigger submit, stop at the captcha, ask), missing data (check DB first; absent → ask, save to DB, continue; never invent salary/phone/personal data). If blocked mid-round: note the exact step+URL, continue other tasks, ask at the end, resume from the saved step.

6 — Draft before replying

Before replying to any recruiter/job-related contact: extract action items from the message (calendar link? CV? scheduling?), analyze the proposal, research the company, present analysis + action items + draft, wait for approval, send.

6b — No public job-search signals

When the user is employed (per users.data), never post public comments/replies expressing job interest or employer outreach on LinkedIn or any public surface. DM blocked → send invite, DM after acceptance; if note limit reached, send bare invite and register pending. Allowed publicly: comments unrelated to the user's own search (community, content, thanks). In doubt → forbidden.

Read the full file on GitHub · 99 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. 2d ago Changed · +22 tokens per session bb11ac801215
  2. 11d ago Changed · +12 lines · +337 tokens per session a0e4c0c727c9
  3. 18d ago Changed · -358 lines · -7,455 tokens per session scan C → A e70215bd5401
  4. 20d ago Changed · +5 lines · +200 tokens per session fd1d5168a36f
  5. 1mo ago Changed · +42 lines · +729 tokens per session scan A → C 83cb5a3c297d
  6. 1mo ago First seen · 398 lines · 8,384 tokens per session scan A cd4cbb223961

Subscribe to this mod's changes

job-seeker AGENTS.md is an instructions file published in the GitHub repository galiprandi/job-seeker (58 stars, last pushed 2d ago), licensed MIT. It adds 2,217 tokens to every session, about $0.0089 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.

Related

Other instructions, from other repositories