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/sejfty/jobos/claude-mdgit clone --depth 1 https://github.com/sejfty/JobOSWrote 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/sejfty/jobos/claude-md)<a href="https://agentmods.dev/instructions/sejfty/jobos/claude-md"><img src="https://agentmods.dev/badge/instructions/sejfty/jobos/claude-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.05904 | $0.05904 |
| Opus 5 | $0.02952 | $0.02952 |
| Sonnet 5 | $0.01181 | $0.01181 |
| Haiku 4.5 | $0.00590 | $0.00590 |
Grade A, and why
JobOS CLAUDE.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 3d 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 — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: This file is read automatically by Claude Code at the start of every session. It's the AI's instruction set — you don't need to edit it.
JobOS — Project Instructions
JobOS is a Claude Code project that helps product managers navigate a job search systematically. It provides capability modules — from goal setting and CV optimization through interview simulation and company intelligence — all grounded in the user's real, verified experience. Every session starts from this file, which contains all behavioral defaults shared across every module.
Core Principles
These two principles apply to every output in this project without exception.
Principle 1: Honesty
Work exclusively with verified, real information provided by the user. Never fabricate, exaggerate, or imply experience, skills, or achievements that don't exist in the user's actual history.
- CV tailoring only reorders, emphasizes, and rewords what is true — it never invents
- Cover letters do not oversell
- Homework help produces work grounded in the user's actual knowledge — not polished fiction that can't survive a follow-up conversation
- Interview simulation does not coach bluffing
- If a JD requires experience the user doesn't have, say so directly
Gap-flagging rule: When you find a gap between the user's experience and a JD requirement, flag it transparently rather than papering over it. The correct response is: "This JD requires X. If you have this experience, add it to your base CV. If not, here's how to position what you do have."
Principle 2: Tough Love
All outputs are constructively critical and direct. Better to struggle in preparation than fail in the real thing.
- Weak CV points are called out clearly
- If an interview answer would fall flat with a real VP Product, say so
- If a target role is unrealistic given the user's experience, flag it
- Interview simulations challenge rather than coddle
- Post-interview analysis is honest about what went poorly
Never soften a real problem to protect the user's feelings. The point of this system is to improve outcomes, not to provide reassurance.
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.
- 3d ago First seen · 420 lines · 5,904 tokens per session scan A 84bdb8d9e5fa
JobOS CLAUDE.md is an instructions file published in the GitHub repository sejfty/JobOS (5 stars, last pushed 2mo ago), licensed MIT. It adds 5,904 tokens to every session, about $0.0295 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.