html-report

A single-file web dashboard built from your job tracker and application records. It opens directly in a browser without a server or extra software.

In plain words
What is it for?
Use it to create an application-tracking report, choose where to save the HTML file, and optionally receive instructions to open it.
Why use it?
It gives you one place to review application history and outcomes instead of inspecting CSV rows and folders separately.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/madslorentzen/ai-job-search/html-report
Clone the repo
git clone --depth 1 https://github.com/MadsLorentzen/ai-job-search

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,233 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02233
Opus 5 $0.00000 $0.01117
Sonnet 5 $0.00000 $0.00447
Haiku 4.5 $0.00000 $0.00223

Measured 2d ago against content hash 36a41dbe56aa, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

html-report 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 2d 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.

Origin

Copies of this mod

2 near-identical copies found in the catalogue:

.claude/commands/html-report.md · 147 lines

How it starts

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

/html-report - Generate Application Tracker Dashboard

Generate a self-contained HTML dashboard from job_search_tracker.csv and the application archives under documents/applications/. The output is a single .html file — no server, no dependencies — that can be opened directly in a browser.

Step 0: Parse Arguments

  • No argument → output to reports/application-dashboard.html
  • A path argument (e.g. /html-report ~/Desktop/report.html) → use that path
  • --open flag → after writing, tell the user to open the file (cannot open a browser directly)

Create reports/ if it does not exist.


Step 1: Collect Data

Read in parallel:

  1. job_search_tracker.csv — the primary source. Parse every row into a record with fields: date, company, sector, role, role_type, channel, status, contact_person, fit_rating, notes, cv_file, cover_letter_file, source, deadline

    Rows written before deadline existed have thirteen fields and no fourteenth value. Treat the missing field as empty - never drop the row, and never infer a deadline from its date.

  2. documents/applications/*/outcome.md — for each resolved application, read the outcome file to get the exact interview stages reached (the checkboxes) and any notes. Merge this into the matching tracker row by company+role fuzzy match (lowercase, ignore punctuation). If an archive exists for a row but there is no match, attach it as extra context anyway.

Status normalisation — map tracker values to six canonical buckets before computing stats:

  • draftedDrafted (documents written by /apply, not yet submitted)
  • appliedActive (resume submitted, no further signal)
  • interviewInterview
  • offerOffer
  • hiredHired
  • rejected / no_response / no response / offer_declined / offer declined / withdrawnRejected/Closed
  • anything else → Rejected/Closed, and name the unrecognised value once in the status breakdown — matching is case-insensitive

Read the full file on GitHub · 147 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. 2d ago First seen · 147 lines · 0 tokens per session scan A 36a41dbe56aa

Subscribe to this mod's changes

html-report is a command published in the GitHub repository MadsLorentzen/ai-job-search (39,400 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,233 tokens. 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.