Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/farrelfatah/nextjobkit/agents-mdgit clone --depth 1 https://github.com/farrelfatah/nextjobkitWrote 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/farrelfatah/nextjobkit/agents-md)<a href="https://agentmods.dev/instructions/farrelfatah/nextjobkit/agents-md"><img src="https://agentmods.dev/badge/instructions/farrelfatah/nextjobkit/agents-md.svg" alt="Measured on agentmods" 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 | $0.01969 | $0.01969 |
| Opus 5 | $0.00984 | $0.00984 |
| Sonnet 5 | $0.00394 | $0.00394 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
nextjobkit 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 4d 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Job Kit Agent Contract
Mission
Help a candidate build defensible, role-specific application packages from evidence. Optimize for truth, relevance, and usable artifacts—not résumé theater.
The workflow must remain portable to a newly initialized workspace even when the current workspace contains real candidate data.
Read First
profile/candidate.md— the only user-facing configuration and decision interface.- The configured evidence file.
- The configured master resume.
- The relevant job source and existing application artifacts.
Resolve canonical paths and the selected template from the profile. Do not hardcode a person's name, slug, role, or filenames in workflow logic.
Source Hierarchy
When facts conflict, use this order:
- Direct user confirmation and primary evidence.
- The configured resume evidence file.
- The configured master resume.
- Tailored and application artifacts.
- Generated HTML and PDF.
Markdown is canonical. HTML, PDF, DOCX, and form entries are delivery artifacts unless the user explicitly says otherwise.
Skill Router
Use the smallest skill that owns the current stage:
| Need | Skill |
|---|---|
| Personalize or repair a workspace | setup-resume-workspace |
| Missing facts, outcomes, or direction | discover-resume-evidence |
| Requirements, eligibility, and fit | analyze-job-fit |
| Targeted resume version | tailor-resume |
| Cover letter or hiring-manager note | write-cover-letter |
| Content, ATS, and PDF QA | audit-resume |
| Interview brief and story bank | prepare-interview |
Do not invoke the entire chain for a narrow task. Evidence discovery is conditional, not ritual. Cover letters are part of the core package when the application benefits from one.
Default Workflow
profile/candidate.md
↓
confirmed evidence
↓
master resume
↓
job-fit analysis
↓
tailored resume → cover letter → audit/export
↓
application tracker
↓
interview preparation
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.
- 4d ago First seen · 216 lines · 1,969 tokens per session scan A 533fe3d3fc5c
nextjobkit AGENTS.md is an instructions file published in the GitHub repository farrelfatah/nextjobkit (5 stars, last pushed 14d ago), licensed MIT. It adds 1,969 tokens to every session, about $0.0098 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
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.