expiration-tracking

expiration-tracking is a skill for Claude Code from leopu00/job-hunter-team. It costs 29 tokens per session (690 once invoked), scanned A, original, MIT.

A tool for finding application deadlines in job descriptions. It returns a date only when the text matches supported date formats with high confidence.

In plain words
What is it for?
Use it while adding or enriching a job listing, and when answering a user's explicit question about its deadline.
Why use it?
It reduces the risk of inventing or misreading a deadline. It also prevents deadline information from becoming an automatic reminder or prompt.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is Bash(python3 /app/shared/skills/deadline_extract.py *), Bash(python3 /app/shared/skills/expiration_alerts.py *).

Good fit Use it while adding or enriching a job listing, and when answering a user's explicit question about its deadline.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/leopu00/job-hunter-team
agentmods
npx agentmods add skills/leopu00/job-hunter-team/expiration-tracking

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 expiration-tracking

README.md
[![agentmods](https://agentmods.dev/badge/skills/leopu00/job-hunter-team/expiration-tracking/github.svg)](https://agentmods.dev/skills/leopu00/job-hunter-team/expiration-tracking)
Your own site
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/expiration-tracking"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/expiration-tracking/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 expiration-tracking

Your own site · 80×15
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/expiration-tracking"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/expiration-tracking.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 690 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 60
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
How audits are shown
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.00029 $0.00690
Opus 5 $0.00015 $0.00345
Sonnet 5 $0.00006 $0.00138
Haiku 4.5 $0.00003 $0.00069

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

Security

Grade A, and why

expiration-tracking 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 11d 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.

agents/_skills/expiration-tracking/SKILL.md · 61 lines

How it starts

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

expiration-tracking — deadline data on request

Deadline data helps the user evaluate opportunities. Preserve it accurately, but do not turn it into a reminder, a prompt to apply, or a measure of progress.

A. Scout/Analista: estrazione deadline dal JD

Quando inserisci una nuova position (Scout) o quando arricchisci la JD (Analista), passa il testo per deadline_extract:

# Direct CLI: estrae da stdin o --jd
echo "$JD_TEXT" | python3 /app/shared/skills/deadline_extract.py
# → 2026-06-15 (ISO date) o stringa vuota

# Inline nel db_insert.py position
deadline_iso=$(echo "$JD_TEXT" | python3 /app/shared/skills/deadline_extract.py)
if [ -n "$deadline_iso" ]; then
  python3 /app/shared/skills/db_insert.py position \
    --title "$TITLE" --company "$COMPANY" --url "$URL" \
    --jd-text "$JD_TEXT" \
    --deadline "$deadline_iso"  # ← nuovo, F-4
fi

Il parser è conservativo (solo ISO, dd/mm/yyyy EU, Month dd[, yyyy] EN/IT, "expires in N days"). Se non trova un match ad alta confidenza restituisce stringa vuota → meglio NULL nel DB che data inventata.

C. Deadline information, only on request

Use this section only while answering the user's explicit question about the deadline of a position or application. Never schedule it, send it proactively, or forward its output as a notification.

Run: python3 /app/shared/skills/expiration_alerts.py --user-requested

The output is factual deadline information for positions already in the user's records, for example: [DEADLINE] Sisal Data Analyst (PASS 7.5) — expires 2026-05-18 (tomorrow).

B. Re-check periodica positions vecchie (Analista) — DA FARE

Estensione futura della skill liveness-check: ogni 6h, refetch URL delle positions in status IN ('scored', 'ready') con last_checked < NOW() - 12h. Se l'URL ritorna 404 / "no longer accepting" → flip a status='expired' + nota. Out of scope per F-4 iniziale; il bottom-up dei deadline catturati dal JD copre la maggior parte dei casi.

Anti-patterns

Read the full file on GitHub · 61 lines

Files

What ships with it

6 files 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.

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. 11d ago First seen · 61 lines · 29 tokens per session scan A 732171cbedd9

Subscribe to this mod's changes

expiration-tracking is a skill published in the GitHub repository leopu00/job-hunter-team (49 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 690 once invoked, about $0.0001 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.