infer-status

infer-status is a skill for Claude Code from jain777/jobclaw-skills. It costs 75 tokens per session (1,478 once invoked), scanned A, original, MIT.

An application-tracking tool that determines a job application's current status from signals such as email type, existing status, elapsed time, and portal state.

In plain words
What is it for?
It is for updating application records after recruiting emails or portal changes, including statuses such as screening, interview, offer, rejected, withdrawn, or ghosted.
Why use it?
It turns scattered application updates into one standard status and a clear next action with a due date.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the jobclaw-skills plugin — 20 skills shipped together

Good fit It is for updating application records after recruiting emails or portal changes, including statuses such as screening, interview, offer, rejected, withdrawn, or ghosted.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/jain777/jobclaw-skills/infer-status
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 jain777/jobclaw-skills --skill infer-status
Clone the repo
git clone --depth 1 https://github.com/jain777/jobclaw-skills

Made for: Claude Code.

Or install jobclaw-skills, the plugin that ships this one along with the rest of its 20 skills.

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 infer-status

README.md
[![agentmods](https://agentmods.dev/badge/skills/jain777/jobclaw-skills/infer-status/github.svg)](https://agentmods.dev/skills/jain777/jobclaw-skills/infer-status)
Your own site
<a href="https://agentmods.dev/skills/jain777/jobclaw-skills/infer-status"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/infer-status/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 infer-status

Your own site · 80×15
<a href="https://agentmods.dev/skills/jain777/jobclaw-skills/infer-status"><img src="https://agentmods.dev/badge/skills/jain777/jobclaw-skills/infer-status.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 75 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,478 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.00075 $0.01478
Opus 5 $0.00037 $0.00739
Sonnet 5 $0.00015 $0.00296
Haiku 4.5 $0.00007 $0.00148

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

Security

Grade A, and why

infer-status 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.

skills/infer-status/SKILL.md · 105 lines

How it starts

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

infer-status

Map signals → status using the taxonomy decision table — no invention. Hard rules: ../_shared/RULES.md. All enums, the decision table, the ghosting rule, and the offer-accept guardrail live in ../../knowledge/status/taxonomy.md.

Inputs

Per-application signals (JSON; single or array)

{
  "job":                    { "company": "...", "role": "...", "job_id": "..." },
  "current_status":         "applied | screening | assessment | interview | final-round | offer | accepted | rejected | withdrawn | ghosted",
  "triage_class":           "rejection | screen | interview-invite | assessment | offer | recruiter-outbound | info | request-info | spam | other | null",
  "days_since_apply":       "number | null",
  "days_since_last_contact":"number | null",
  "portal_state":           "string | null",     // verbatim portal label if scraped, e.g. "Application Rejected"
  "as_of":                  "YYYY-MM-DD"
}

Or --in inbox/triage-<date>.json to read triage records directly; the skill joins triage → applications by (company, role) or job_id and pulls current_status from tracker.json if present.

Flags

  • --ghost-days N — override the 14-day ghosting threshold.
  • --update tracker.json — write the new status back into tracker.json (only fields that changed).
  • --confirm-acceptthe only way to transition offer → accepted. Without it, an offer stays at offer.

Method

  1. Read the taxonomy decision table and the ghosting rule.

  2. Resolve triage_class if absent by reading the latest inbox/triage-<date>.json for this job (if present). Otherwise skip the email branch and use only portal + recency signals.

  3. Apply the decision table. (triage_class × current_status) → (next_status, suggested_action). Terminal email classes (rejection, offer) trump current status; info / request-info / spam never change status.

  4. Override on portal signal if present. Portal labels are ground truth when they exist (e.g., portal_state: "Application Rejected"rejected regardless of email). Record the override in rationale.

Read the full file on GitHub · 105 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. 12d ago First seen · 105 lines · 75 tokens per session scan A e129734f5938

Subscribe to this mod's changes

infer-status is a skill published in the GitHub repository jain777/jobclaw-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 75 tokens to every session and 1,478 once invoked, about $0.0004 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