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 skills add Mahashwetha/Job-search-email-system-claude --skill remove-hot-jobgit clone --depth 1 https://github.com/Mahashwetha/Job-search-email-system-claudeWrote 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/skills/mahashwetha/job-search-email-system-claude/remove-hot-job)<a href="https://agentmods.dev/skills/mahashwetha/job-search-email-system-claude/remove-hot-job"><img src="https://agentmods.dev/badge/skills/mahashwetha/job-search-email-system-claude/remove-hot-job/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/skills/mahashwetha/job-search-email-system-claude/remove-hot-job"><img src="https://agentmods.dev/badge/skills/mahashwetha/job-search-email-system-claude/remove-hot-job.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.00090 | $0.00737 |
| Opus 5.5 | $0.00036 | $0.00295 |
| Sonnet 5.5 | $0.00018 | $0.00147 |
| Haiku 4.5 | $0.00009 | $0.00074 |
Grade A, and why
remove-hot-job 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 20d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Remove Hot Jobs
Manage the hot jobs list in daily_hot_jobs.json. Hot jobs are sticky LinkedIn listings shown at the top of the daily email, 5 per category (or 8 for Tech Lead / AI categories).
Key concepts
- current_jobs: dict of category → list of job objects. Clear a slot by removing from this list — it backfills on next run.
- blocklist: list of
[company, title]pairs. Blocklisted jobs never reappear in that category. - If a job was applied to (company is in the tracker), do NOT blocklist it — the system auto-removes tracker companies naturally.
- If a job is being dismissed without applying, blocklist it so it doesn't come back.
Categories (exact keys in JSON)
Senior JavaBackend JavaProduct OwnerAssistant Project ManagerTech Lead / Lead DeveloperAI / GenAI Engineer
What to do based on what the user says
Remove a single job (applied or dismissed) — remove it from current_jobs[category]. If dismissed (not applied), also add [company.lower(), title.lower()] to blocklist.
Clear all jobs in a category — set current_jobs[category] = []. For each job, blocklist it unless the user says they applied to it (or it's already in the tracker).
Remove from blocklist — find and delete the matching [company, title] pair from the blocklist array.
List current hot jobs for a category — read and print current_jobs[category].
Steps
- If the user didn't specify which jobs they applied to vs dismissed, ask — applied jobs should NOT be blocklisted.
- For each job to blocklist, run the script:
Run from the project root (python .claude/skills/remove-hot-job/scripts/blocklist_job.py "Company Name" "Job Title"claude-job-agent/).- Title is optional — omit to blocklist all jobs from that company.
- The script removes from
current_jobsAND adds to blocklist in one shot. - Uses
ensure_ascii=Falseso no encoding issues.
- Confirm output to the user: removed from current_jobs + blocklisted.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 20d ago Changed 32450dfbf139
- 1mo ago Changed · +7 lines 15e12a9c7c1f
- 1mo ago First seen · 52 lines · 90 tokens per session scan A d380ab559e90
remove-hot-job is a skill published in the GitHub repository Mahashwetha/Job-search-email-system-claude (10 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 737 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
kochab
Kochab, a personalized resume-based job-search assistant that runs a recurring scan and everything downstream of it. Use when the user wants to start or run a job search, shares a resume, or says "set up my job scan," "find roles that fit my resume," or "what should I apply to." Also use to tailor a resume, draft a…
managing-up
AUTO-TRIGGER: Apply this skill when the user is navigating the relationship with their own manager, including a CEO, CRO, VP, or any person they report to directly. Trigger phrases include: "my CEO keeps changing priorities," "my manager is micromanaging," "how do I disagree with my boss," "my CRO doesn't understand…
scenario-zbrush-expert
Use when an agent drives Maxon ZBrush 2026 for any task (sculpt in ZBrush, DynaMesh, ZRemesher, UVs, export, polypaint, posing, 3D print, clean up an AI mesh in ZBrush), when writing ZBrush Python (zbrush.commands) or ZScript, when the ZBrush bridge is not answering, a palette path or set() does nothing, a scripted…
customer-journey-map
Construye un mapa de recorrido del cliente para un producto, servicio o experiencia. Úsalo cuando se te pida mapear un recorrido del cliente, crear un viaje del usuario, documentar puntos de contacto y puntos de fricción, o diseñar un mapa de experiencia. Produce un mapa de recorrido completo con etapas, puntos de…
feature-prioritisation
Aplica marcos de priorización (RICE, MoSCoW, Kano, ICE, Opportunity Scoring) para clasificar características e items del backlog. Úsalo cuando se te pida priorizar características, clasificar un backlog, decidir qué construir a continuación, o evaluar compensaciones entre ideas competidoras. Produce una lista de…
design-handoff-brief
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context…