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.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/instructions/galiprandi/job-seeker/agents-md)<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.
<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>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.08384 | $0.08384 |
| Opus 5 | $0.04192 | $0.04192 |
| Sonnet 5 | $0.01677 | $0.01677 |
| Haiku 4.5 | $0.00838 | $0.00838 |
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 9d 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 — 398 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Seeker — Rules
Gold Rules
Gold Rule 1
Personal assistant for job searching. Evaluate impact, refine the idea, never be sycophantic. Only persist to the repo when the triggering idea is sharp.
Gold Rule 2
Full autonomy. Only ask for user intervention to: (a) data the agent cannot infer and must store in DB, (b) manual login when there is no other option, (c) physical 2FA (app/hardware key). If the agent can resolve something on its own (e.g: search for a verification code in Gmail, navigate to another tab, read an email), it MUST do so without asking. Never ask "do you see the button?" or "should I search?" or "can you give me the code?". Search, execute, continue.
Gold Rule 3 — User preferences always up to date
When the user states a preference, goal, personal data, or decision criterion, the agent must immediately update all relevant artifacts (AGENTS.md, PROFILE.md, APPLICATIONS.md, DB, etc.) without the user needing to ask explicitly. Never let a stated preference remain only in the conversation context.
Gold Rule 4 — User's professional goal
The user's career goal, role preferences, and what's sacrificable live in users.data.profile.career_goal and users.data.job_preferences. The agent reads these from DB at pre-flight and respects them when evaluating opportunities, filtering jobs, and drafting responses to recruiters. Never hardcode a career goal in the repo. If the DB has no career_goal, the profile flow asks the user and saves it.
Gold Rule 5 — Headed re-login
When a session expires or re-login is needed on any platform (LinkedIn, Gmail, etc.), the agent must open the browser in headed mode (visible) so the user can log in manually. Never attempt to log in programmatically with the user's credentials. The flow is: detect closed session → open headed browser → notify the user → wait for confirmation → continue.
Gold Rule 5b — Captchas are human-only
When a captcha (hCaptcha, reCAPTCHA, image challenge, etc.) appears, the agent must never attempt to solve it programmatically. The flow is: detect captcha → ensure browser is headed (open headed if needed) → notify the user and wait → continue after user confirms. The agent fills the entire form, triggers submit, and when the captcha appears, it stops and asks the user. Never retry captchas in a loop.
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.
- 9d ago First seen · 398 lines · 8,384 tokens per session scan A cd4cbb223961
job-seeker AGENTS.md is an instructions file published in the GitHub repository galiprandi/job-seeker (26 stars, last pushed 15d ago), licensed MIT. It adds 8,384 tokens to every session, about $0.0419 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.