Borrowing it
Nothing to install: this file belongs to OmriH-Elister/job-search-mcp. 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/OmriH-Elister/job-search-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/OmriH-Elister/job-search-mcpWrote 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/omrih-elister/job-search-mcp/agents-md)<a href="https://agentmods.dev/instructions/omrih-elister/job-search-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/omrih-elister/job-search-mcp/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/omrih-elister/job-search-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/omrih-elister/job-search-mcp/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.00742 | $0.00742 |
| Opus 5 | $0.00371 | $0.00371 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
job-search-mcp 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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- job-search-mcp CLAUDE.md — 97% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Job Search Harness
Operating spec for the automated job search pipeline. Authoritative. If this file and conversational context disagree, ask.
All candidate-specific data (identity, target roles, seed list, exclusions)
lives in config.json — see config.example.json. Nothing personal belongs
in this file.
Goal
Keep a steady flow of applications going to well-matched roles with minimal manual effort, gated on a single human decision: cover letter approval. Everything else — scanning, matching, filtering, drafting, submitting — is automated.
The pipeline is NOT paused for in-flight offers; it runs full-tilt regardless of interview status.
Scan workflow
After a scan, silently reject:
- Companies already applied to (see
data/previously_applied.json) - Lateral moves — role tiers the candidate has configured as below target
- False positives — product pages, marketing URLs, non-job pages
For each genuinely new match:
- Draft the cover letter immediately
- Display it to the candidate
- Pause ONLY for letter confirmation
Do NOT ask "want me to approve these?" and do NOT list matches separately from their letters. Once a letter is confirmed, submit immediately (ATS, falling back to email).
Zero-match runs: if a full scan yields no genuinely new matches after
filtering, automatically research and add 5 new relevant companies to
config.json company_seed_list before ending the run. Focus on categories
adjacent to the configured targets (startups, MSSPs, consulting firms, larger
firms with local offices) that are not already listed. The pipeline treats
"no findings" as a coverage gap, not a success state.
Excluded companies
Configured in config.json (current employer and any others the candidate
lists). Never apply to an excluded company, even on a strong match.
Infrastructure
| Item | Value |
|---|---|
| Root | repo directory (scripts derive paths from their own location) |
| Image | job-search-mcp:latest |
| Data volume | <root>\data -> /data (nightly AND MCP server must share this) |
| CV volume | JOB_SEARCH_CV_DIR env var -> /cvs:ro (defaults to <root>\cvs) |
| Scheduled task | JobSearchNightlyScan, daily 22:00 |
| Wrapper | run_nightly.ps1 |
| Seed list | company_seed_list in config.json |
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.
- 11d ago First seen · 86 lines · 742 tokens per session scan A c799716e2b86
job-search-mcp AGENTS.md is an instructions file published in the GitHub repository OmriH-Elister/job-search-mcp (0 stars, last pushed 17d ago), licensed MIT. It adds 742 tokens to every session, about $0.0037 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-31.
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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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).