email-monitor

email-monitor is a skill for Claude Code from leopu00/job-hunter-team. It costs 116 tokens per session (1,225 once invoked), scanned A, original, MIT.

A monitor for a dedicated email inbox where the user forwards job alerts from employment websites. It reads those alerts and turns them into job-position records.

In plain words
What is it for?
It helps collect overnight and periodic alerts from sites such as LinkedIn, Glassdoor, Indeed, and other job boards before normal web sourcing begins.
Why use it?
The alerts have already been filtered by the user, so this can provide relevant jobs without repeatedly searching unrelated websites. It also avoids duplicate imports and excessive mailbox polling.

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/email_monitor.py *), Bash(python3 /app/shared/skills/scout_dedup.py *), Bash(python3 /app/shared/skills/db_insert.py *), Bash(py.

Good fit It helps collect overnight and periodic alerts from sites such as LinkedIn, Glassdoor, Indeed, and other job boards before normal web sourcing begins.

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/email-monitor

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 email-monitor

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/leopu00/job-hunter-team/email-monitor"><img src="https://agentmods.dev/badge/skills/leopu00/job-hunter-team/email-monitor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 116 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,225 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 pass 7 Sept 2026
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.00116 $0.01225
Opus 5 $0.00058 $0.00613
Sonnet 5 $0.00023 $0.00245
Haiku 4.5 $0.00012 $0.00122

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

Security

Grade A, and why

email-monitor 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.

agents/_skills/email-monitor/SKILL.md · 89 lines

How it starts

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

email-monitor — reading forwarded job alerts, at day start

The user creates a dedicated email address (e.g. [email protected]) and sets up forwarding rules in their own client that send us the job alerts (LinkedIn, Glassdoor, Indeed and any other platform that notifies by mail). You read that mailbox and turn the alerts into positions. It is the most accurate source (the alert is already filtered on the target by the user) and the most token-cheap one (no blind scraping).

📍 Optional but recommended. If it is not configured, the team works as before (web sourcing). Nothing is blocked.

When

  • At the start of the work window (day-start): read the email BEFORE web scraping. Overnight alerts are already there.
  • Then at most every ~30 min (the IMAP server rate-limits beyond that, and new alerts do not arrive more often). Do not poll more frequently.
  • Claim the source in STEP 0 (scout-coord): scout_workspace.py claim <agent> email:<box> — one Scout only per mailbox, no collisions.

Procedure

1. Is it configured?

python3 /app/shared/skills/email_monitor.py status

configured=false → the mailbox is not there: skip, do normal web sourcing. any_platform=true means we process the entire dedicated inbox (no narrow from_filters) → every sender the user forwards gets read.

2. Estimate the VOLUME (cheap, no body fetch)

python3 /app/shared/skills/email_monitor.py count

Returns new_total + by_sender. It tells you and the Captain whether this is a manageable volume or a flood. On a flood, the Captain (C-16) tells you how many / which ones to ingest: the goal is that positions reach a score, not to pile up 200 that are never evaluated.

3. Poll → leads

python3 /app/shared/skills/email_monitor.py poll --since-days 1

Every JSONL line is a lead: {"url","source","subject","sender","received_at"}.

  • source = linkedin-email / glassdoor-email / indeed-email for the known providers, email:<domain> for any other platform (generic extraction).
  • Idempotency (Message-ID in state/email_monitor_seen.json) guarantees that a re-run does not reprocess the same alerts.

Read the full file on GitHub · 89 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. 12d ago First seen · 89 lines · 116 tokens per session scan A 6e27203eeb79

Subscribe to this mod's changes

email-monitor is a skill published in the GitHub repository leopu00/job-hunter-team (49 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 1,225 once invoked, about $0.0006 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.