Borrowing it
Nothing to install: this file belongs to muggl3mind/career-manager. 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/muggl3mind/career-manager/main/CLAUDE.mdgit clone --depth 1 https://github.com/muggl3mind/career-managerWrote 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/muggl3mind/career-manager/claude-md)<a href="https://agentmods.dev/instructions/muggl3mind/career-manager/claude-md"><img src="https://agentmods.dev/badge/instructions/muggl3mind/career-manager/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.1 | $0.00465 | $0.00465 |
| Opus 5 | $0.00233 | $0.00233 |
| Sonnet 5 | $0.00093 | $0.00093 |
| Haiku 4.5 | $0.00047 | $0.00047 |
Grade A, and why
career-manager 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 7d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Career Manager
AI-assisted career management pipeline built as Claude Code skills.
Environment
- Use
uv runto execute all Python scripts - If
.venv/doesn't exist:uv venv && uv pip install -r requirements.txt
Script Paths
All pipeline scripts live under job-search/scripts/. Run from the project root with full paths:
uv run job-search/scripts/ops/run_pipeline.py phase1 # correct
uv run scripts/ops/run_pipeline.py phase1 # WRONG — will fail
SKILL.md files use paths relative to their skill directory. Always prefix with the skill folder.
How This Works
- Each skill has a
SKILL.md— read it before executing that skill search-config.jsonandconfig.yamlare generated by the onboarding skill — never edit pipeline scripts to change search queries or scoring- Data ownership:
job-search/data/target-companies.csvandjob-tracker/data/applications.csvare sources of truth - Never edit CSVs directly — use the tracker scripts
First-Time Setup
If config.yaml or search-config.json don't exist, run the onboarding skill first. See README for full setup steps.
Status Briefing
Before running workflows, the router calls scripts/generate_briefing.py for a status snapshot. This is automatic. Do not ask the user to run it.
Testing
uv run python3 scripts/smoke_test.py # verify setup
uv run python3 -m pytest evals/tests/ -v # run test suite
Repo Sync
The public repo at career-manager-public/ is synced from this private repo via scripts/export_public.py. Both repos must stay in sync for skill files.
Before exporting:
uv run python3 scripts/check_sync.py
If divergence is found, resolve before exporting. The export script has a timestamp guard that skips files where the public version is newer, but always verify with check_sync.py first.
After editing skill files in either repo: run check_sync.py --fix to copy the newer version to the other repo, then commit in both.
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.
- 7d ago First seen · 55 lines · 465 tokens per session scan A b1f2c6f7d4d5
career-manager CLAUDE.md is an instructions file published in the GitHub repository muggl3mind/career-manager (24 stars, last pushed 4mo ago), licensed MIT. It adds 465 tokens to every session, about $0.0023 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
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).
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.
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).
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.