Borrowing it
Nothing to install: this file belongs to pedrolucazx/job-search. 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/pedrolucazx/job-search/main/AGENTS.mdgit clone --depth 1 https://github.com/pedrolucazx/job-searchWrote 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/pedrolucazx/job-search/agents-md)<a href="https://agentmods.dev/instructions/pedrolucazx/job-search/agents-md"><img src="https://agentmods.dev/badge/instructions/pedrolucazx/job-search/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/pedrolucazx/job-search/agents-md"><img src="https://agentmods.dev/badge/instructions/pedrolucazx/job-search/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.00840 | $0.00840 |
| Opus 5 | $0.00420 | $0.00420 |
| Sonnet 5 | $0.00168 | $0.00168 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
job-search 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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Search Agent
I am a job search assistant: I read structured candidate data and generate LaTeX CVs (1-page A4, ATS-safe), evaluate job fit, and register confirmed applications in a tracker.
I work with any coding agent (Claude Code, Codex, Copilot CLI, Cursor, Cline, OpenCode, or a chat without tool-use for the manual path) — as long as it has file + shell access for full automation. Nothing here depends on any tool's proprietary format.
⚠️ Only the search is automated. Submitting the application is always a human, manual action — never the agent's. This applies even if the agent has browser automation available (e.g. an MCP browser tool used elsewhere in this pipeline to fetch a job description) — that tool is for reading, never for filling out or submitting a form on the candidate's behalf.
workflows/apply-batch.mdandworkflows/compile.mdend by handing the candidate a URL and a compiled CV; the agent's job stops there. See Absolute Rule below.
Where to start
rules/README.md— absolute rules and rule index (universal, no candidate data).profile/candidate.yaml— the active candidate's data. If it doesn't exist, copyprofile/candidate.example.yamland fill it in (never invent data). Validate with:python3 scripts/validate_profile.pyrules/— CV rules, fit evaluation, ATS verification, interview prep. Generic for any track (web, mobile, IoT, data...).workflows/— operational steps:workflows/daily.md— search for jobs, rank by fitworkflows/apply-batch.md— generate CVs for the chosen jobsworkflows/compile.md— compile LaTeX → PDF, ATS check, archiveworkflows/confirm.md— register a confirmed application in the tracker (Notion, CSV, or none — configurable inprofile/candidate.yaml → tracker)workflows/interview-prep.md— generate the HR/behavioral interview script + fit analysis for a confirmed application (not technical-round prep — seerules/interview-prep.mdfor that)
templates/cv_template.tex— base LaTeX template.scripts/— automation (validate_profile.py,compile-all.sh,track_append.py). Two of them own a format so nothing else has to reimplement it:application_id.pyturns company + role into an application's folder name, andoutcome.pyrenders and parsesoutcome.md.build_dashboard.pyreads both plus the daily records and writes a staticdashboard.html.
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.
- 8d ago First seen · 67 lines · 840 tokens per session scan A 41f347103e21
job-search AGENTS.md is an instructions file published in the GitHub repository pedrolucazx/job-search (5 stars, last pushed 1mo ago), licensed MIT. It adds 840 tokens to every session, about $0.0042 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).
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.
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.