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.
git clone --depth 1 https://github.com/ishandutta2007/Awesome-AI-Job-HuntingWrote 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/commands/ishandutta2007/awesome-ai-job-hunting/html-report)<a href="https://agentmods.dev/commands/ishandutta2007/awesome-ai-job-hunting/html-report"><img src="https://agentmods.dev/badge/commands/ishandutta2007/awesome-ai-job-hunting/html-report/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.
<a href="https://agentmods.dev/commands/ishandutta2007/awesome-ai-job-hunting/html-report"><img src="https://agentmods.dev/badge/commands/ishandutta2007/awesome-ai-job-hunting/html-report.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.02233 |
| Opus 5 | $0.00000 | $0.01117 |
| Sonnet 5 | $0.00000 | $0.00447 |
| Haiku 4.5 | $0.00000 | $0.00223 |
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 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.
This is a copy
100% identical to html-report — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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 --openflag → 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:
-
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,deadlineRows written before
deadlineexisted have thirteen fields and no fourteenth value. Treat the missing field as empty - never drop the row, and never infer a deadline from itsdate. -
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:
drafted→ Drafted (documents written by/apply, not yet submitted)applied→ Active (resume submitted, no further signal)interview→ Interviewoffer→ Offerhired→ Hiredrejected/no_response/no response/offer_declined/offer declined/withdrawn→ Rejected/Closed- anything else → Rejected/Closed, and name the unrecognised value once in the status breakdown — matching is case-insensitive
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.
- 12d ago First seen · 147 lines · 0 tokens per session scan A 36a41dbe56aa
html-report is a command published in the GitHub repository ishandutta2007/Awesome-AI-Job-Hunting (3 stars, last pushed 17d ago), 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. It is 100% identical to html-report, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
new-sdk-app
Create and setup a new Claude Agent SDK application.
review-issue
Review and respond to a GitHub issue.
analyze-codebase
Generate comprehensive analysis and documentation of entire codebase.
tdd
This outlines the development practices and principles we require you to follow. Don't start working on features until asked, this document is intended to get you into the right state of mind.
test
Focused on testing internal logic, not API endpoints.
review
Command "review" from Najeebullah3124/awesome-claude-universe, covering pr review, task 1: product manager review, task 2: developer review, task 3: quality engineer review and task 4: security engineer review.