freehire-mail-triage

freehire-mail-triage is a skill for Claude Code from strelov1/freehire-cli. It costs 96 tokens per session (1,513 once invoked), scanned A, original, MIT.

A command-line workflow for sorting job-application emails into the freehire application tracker. You fetch the messages with your own mail program, then submit and classify them.

In plain words
What is it for?
Importing batches of application emails, deciding what each message means, linking replies to applications, and moving applications forward based on those replies.
Why use it?
It connects an existing mailbox to the tracker without needing a separate mail connector or automatic classifier. It keeps message labels, linked applications, and application stages together.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the freehire plugin — 6 skills, 5 commands shipped together

Good fit Importing batches of application emails, deciding what each message means, linking replies to applications, and moving applications forward based on those replies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/strelov1/freehire-cli/freehire-mail-triage
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.

Any agent
npx skills add strelov1/freehire-cli --skill freehire-mail-triage
Clone the repo
git clone --depth 1 https://github.com/strelov1/freehire-cli

Made for: Claude Code.

Or install freehire, the plugin that ships this one along with the rest of its 6 skills, 5 commands.

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 freehire-mail-triage

README.md
[![agentmods](https://agentmods.dev/badge/skills/strelov1/freehire-cli/freehire-mail-triage/github.svg)](https://agentmods.dev/skills/strelov1/freehire-cli/freehire-mail-triage)
Your own site
<a href="https://agentmods.dev/skills/strelov1/freehire-cli/freehire-mail-triage"><img src="https://agentmods.dev/badge/skills/strelov1/freehire-cli/freehire-mail-triage/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 freehire-mail-triage

Your own site · 80×15
<a href="https://agentmods.dev/skills/strelov1/freehire-cli/freehire-mail-triage"><img src="https://agentmods.dev/badge/skills/strelov1/freehire-cli/freehire-mail-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 96 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,513 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.
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.00096 $0.01513
Opus 5 $0.00048 $0.00757
Sonnet 5 $0.00019 $0.00303
Haiku 4.5 $0.00010 $0.00151

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

Security

Grade A, and why

freehire-mail-triage 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.

skills/freehire-mail-triage/SKILL.md · 119 lines

How it starts

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

Sorting application mail into the tracker

Needs a key: freehire auth login --token fhk_… (or FREEHIRE_TOKEN).

freehire does not fetch mail. You bring your own client — himalaya, mbsync, notmuch, the Gmail API, anything that can emit JSON — and hand the result over. In exchange you get the inbox wired into the application tracker without paying for a mail connector or a classifier.

The loop is four steps, and then two queues that only a human's verdict can empty:

# 1. Your client fetches; you shape it into the batch and push it.
himalaya envelope list --output json | jq '[.[] | {
    external_id: .message_id, from_addr: .from.addr, from_name: .from.name,
    subject: .subject, received_at: .date }]' | freehire inbox push

# 2. Ask for what still needs judging, with the text to judge.
freehire --json inbox list --unclassified --body --limit 50

# 3. You decide what each message is (and which application it belongs to).
# 4. Record the verdict — one call sets the label, the link, and the stage.
freehire inbox triage 812 rejection --slug go-dev-acme-t35nijto
freehire inbox triage 813 interview_invitation --slug data-eng-globex-9f2k1a0z --confidence 0.9

external_id is the deduplication key — use the message's Message-ID. Pushing the same id again updates that message rather than storing a copy, so re-running your sync over an overlapping window is safe and cheap. It never un-reads a message, never resurrects one the user deleted, and never overwrites a verdict you recorded. Batches are capped at 100 messages.

Use inbox list --body, not inbox read, when sweeping. Opening a message marks it read, and read is meant for "the user asked to see this one". Sweeping a backlog with read would silently zero the user's unread count. The listing returns the same readable text (HTML-only ATS mail arrives stripped to text) and marks nothing.

Signalsacknowledgement, screening, interview_invitation, assessment, offer, rejection, info_request, incomplete_application, other. A forward signal on a linked message advances that application's stage; a settled application (rejected/accepted/withdrawn) is never dragged back into the pipeline.

Read the full file on GitHub · 119 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. 11d ago First seen · 119 lines · 96 tokens per session scan A 0cc38f89f177

Subscribe to this mod's changes

freehire-mail-triage is a skill published in the GitHub repository strelov1/freehire-cli (5 stars, last pushed 4d ago), licensed MIT. It adds 96 tokens to every session and 1,513 once invoked, about $0.0005 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-31.

Related

Other skills, from other repositories

resume-tailoring

Methodology for tailoring a resume to a job description honestly and effectively — fit analysis, gap handling, keyword mirroring, fast-learner framing, and primary-over-secondary emphasis. Use whenever curating or rewriting a resume for a specific role.

snehag01/rebound · 53 tokens

alive:system-cleanup

The world feels messy. Stale tasks, orphan folders, v2 remnants, unsaved sessions — entropy is accumulating and needs to be addressed before it compounds. Scans across all walnuts, then surfaces issues one at a time.

alivecontext/alive · 52 tokens

alive:world

The human doesn't know what to work on, or wants to see everything at once. They need the big picture — what's active, what's stale, what needs attention. Renders a live world view grouped by ALIVE domain, then routes to open, tidy, find, history, or map.

alivecontext/alive · 63 tokens

alive:bundle

Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.

alivecontext/alive · 34 tokens

alive:settings

The human wants to adjust how the system behaves — not what it contains, but how it feels. Voice, rhythm, preferences, walnut-level config, full permissions toggleable, named squirrel config, action logging toggle. The system adapting to them. Routes to preferences.yaml or walnut config.yaml depending on scope. For…

alivecontext/alive · 84 tokens

alive-cleanup

System maintenance -- stale tasks, orphan folders, unsaved sessions, world health check.

alivecontext/alive · 20 tokens