job-search-hq: Instructions file for Claude Code

CLAUDE.md

job-search-hq CLAUDE.md is an instructions file for Claude Code from Miracle-Aligner/job-search-hq. It costs 1,288 tokens per session, scanned A, original, MIT.

A set of project instructions for an agent-maintained job-search tracker. It explains where the job data, viewer, settings, validation rules, and automation skills live.

In plain words
What is it for?
It helps maintain a job-search CRM, update vacancy data, run validation, manage configuration, and work with the self-contained HTML viewer.
Why use it?
It gives the coding agent the project context and conventions it needs to work consistently without guessing where files or data belong.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: reads .claude/ paths; mentions Claude Code.

This is Miracle-Aligner/job-search-hq's own configuration. It tells Claude Code how to work on job-search-hq itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything job-search-hq configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Miracle-Aligner/job-search-hq. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Miracle-Aligner/job-search-hq/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/Miracle-Aligner/job-search-hq

Made for: Claude Code.

Wrote 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.

agentmods badge for job-search-hq CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/miracle-aligner/job-search-hq/claude-md/github.svg)](https://agentmods.dev/instructions/miracle-aligner/job-search-hq/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/miracle-aligner/job-search-hq/claude-md"><img src="https://agentmods.dev/badge/instructions/miracle-aligner/job-search-hq/claude-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.

agentmods 80×15 button for job-search-hq CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/miracle-aligner/job-search-hq/claude-md"><img src="https://agentmods.dev/badge/instructions/miracle-aligner/job-search-hq/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,288 This file is loaded in full into every session.
When invoked 1,288 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01288 $0.01288
Opus 5 $0.00644 $0.00644
Sonnet 5 $0.00258 $0.00258
Haiku 4.5 $0.00129 $0.00129

Measured 12d ago against content hash dd3ad6d40710, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

job-search-hq 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 12d 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.

CLAUDE.md · 74 lines

How it starts

The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Job Search HQ — Claude Code project context

An agent-maintained job-search CRM. A single JSON board is the source of truth, a self-contained static HTML file is the viewer, config files hold the knobs, and a suite of Claude Code skills do the work. No frameworks, zero runtime deps (Python stdlib only; dev/CI tooling may add dev-only deps).

Where things live

  • data/vacancies.json — source of truth, a v2 envelope: { "schemaVersion": 2, "vacancies": [ … ] }. Gitignored (real data). The committed demo is data/vacancies.sample.json (synthetic, regenerated by scripts/make_demo.py). scripts/board.py is the one place that knows the shape.
  • job-search-hq.html — the viewer. Carries the data + app config baked into <script type="application/json"> blocks (sentinel-bounded) so file:// works anywhere. Always baked from the sample — real data only ever lands in the gitignored job-search-hq.local.html (via serve.py).
  • config/app.json · scoring.json · platforms.json · sources.json. One source of truth per concern; *.local.json (gitignored) overrides merge on top.
  • schema/vacancy.schema.json — the data contract. validate.py checks against it (via the stdlib mini-validator in scripts/schema_check.py).
  • profile/candidate.md + profile.json (gitignored real; *.example.* committed) and cv/ (gitignored CVs). Read by assessment skills at scoring time.
  • docs/schema.md, rubric.md (generated by gen_rubric.py), scheduling.md.
  • scripts/serve.py (live server) · build.py (validate+bake) · bake.py · validate.py · score.py · migrate.py · init.py · make_demo.py · gen_rubric.py · board.py · config_util.py · schema_check.py.
  • .claude/skills/ — the skills (see below). tests/ — stdlib unittest.

Conventions

  • Single source of truth per concern. Data → data/. Config → config/. Schema → schema/. Don't duplicate constants across Python/JS/CSS — bake.py injects {app, scoring, platforms} into the HTML so the UI can't drift.
  • Never commit real data. Real data/vacancies.json, profile/candidate.md, profile/profile.json, profile/cv/*, config/*.local.json, and job-search-hq.local.html are gitignored. Work against the *.sample/*.example files. The committed HTML and the Pages demo are sample-only.
  • After editing data, run python3 scripts/build.py --real (validates real data + rebakes the gitignored local snapshot). build.py with no args rebuilds the committed demo from the sample (what CI's drift check runs).
  • Score via the script. Pick 5 honest sub-scores per docs/rubric.md, then python3 scripts/score.py compute <tech> <comp> <level> <company> <appeal> [risk]. Weights/tiers come from config/scoring.json. Tier is derived — never hand-set.
  • Pipeline-locked statuses are sacred. Never overwrite applied, hr_screen, tech_interview, final, offer, rejected during a sweep.
  • altLinks are verified, not synthesised — every URL must return a role-relevant 200.
  • Escape untrusted text in the viewer (esc/safeUrl/sanitizeRich); statusDetail is the one field allowed a small formatting-tag allowlist.

Read the full file on GitHub · 74 lines

Changes

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.

  1. 12d ago First seen · 74 lines · 1,288 tokens per session scan A dd3ad6d40710

Subscribe to this mod's changes

job-search-hq CLAUDE.md is an instructions file published in the GitHub repository Miracle-Aligner/job-search-hq (1 stars, last pushed 3mo ago), licensed MIT. It adds 1,288 tokens to every session, about $0.0064 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.

Related

Other instructions, from other repositories

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.

github/spec-kit · 7,126 tokens

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens