track-application

track-application is a skill for Claude Code from tmargolis/career-navigator. It costs 63 tokens per session (4,451 once invoked), scanned A, original, Apache-2.0.

Uma ferramenta para registrar candidaturas a empregos em um arquivo de acompanhamento. Ela mantém dados da vaga e pode registrar mudanças de etapa, contatos, entrevistas, ofertas, resultados e próximos acompanhamentos.

In plain words
What is it for?
Serve para adicionar ou atualizar candidaturas, registrar contatos e entrevistas, guardar ofertas e resultados e programar lembretes de acompanhamento.
Why use it?
Acompanhar candidaturas em conversas soltas pode fazer informações e prazos se perderem. O registro reúne o histórico de cada candidatura em uma estrutura organizada.

Skill for Claude Code

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

Part of the career-navigator plugin — 46 skills, 3 MCP servers shipped together

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.

agentmods
npx agentmods add skills/tmargolis/career-navigator/track-application
Any agent
npx skills add tmargolis/career-navigator --skill track-application
Clone the repo
git clone --depth 1 https://github.com/tmargolis/career-navigator

Made for: Claude Code.

Or install career-navigator, the plugin that ships this one along with the rest of its 46 skills, 3 MCP servers.

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 track-application

README.md
[![agentmods](https://agentmods.dev/badge/skills/tmargolis/career-navigator/track-application.svg)](https://agentmods.dev/skills/tmargolis/career-navigator/track-application)
Your own site
<a href="https://agentmods.dev/skills/tmargolis/career-navigator/track-application"><img src="https://agentmods.dev/badge/skills/tmargolis/career-navigator/track-application.svg" alt="Measured on agentmods" height="20"></a>
Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,451 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00063 $0.04451
Opus 5 $0.00032 $0.02226
Sonnet 5 $0.00013 $0.00890
Haiku 4.5 $0.00006 $0.00445

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

Security

Grade A, and why

track-application 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 5d 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/track-application/SKILL.md · 384 lines

How it starts

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

Log or update an application record. Extract as much as possible from what the user said before asking for anything.

Application data uses the split layout defined in references/tracker-schema.md — read it before any read or write.

Application Record Schema

An application lives across three files. Never put notes, stage_history, or contacts inside a tracker.json row.

Summary rowtracker.jsonapplications[]:

{
  "id": "app-<company-slug>-<role-keywords>",
  "application": "<company> — <role>",
  "company": "...",
  "role": "...",
  "job_link": "...",
  "req_id": null,
  "salary_range": "...",
  "location": "...",
  "resume_version": null,
  "date_applied": "YYYY-MM-DD",
  "status": "applied | phone_screen | interview | offer | accepted | rejected | withdrew | ghosted",
  "detail_file": "applications/app-<company-slug>-<role-keywords>.json",
  "contacts_file": "contacts/<company-slug>.json",
  "notes_count": 0,
  "stage_count": 1,
  "contact_count": 0,
  "latest_stage": "applied",
  "latest_stage_date": "YYYY-MM-DD",
  "follow_up_date": "YYYY-MM-DD",
  "next_step": "...",
  "priority": "high | medium | low | null",
  "referral": { "name": "...", "relationship": "colleague | friend | recruiter | other" },
  "offer": {
    "base": "...",
    "bonus": "...",
    "equity": "...",
    "benefits_notes": "...",
    "deadline": "YYYY-MM-DD",
    "decision": null
  },
  "outcome": "pending | hired | rejected | withdrew",
  "outcome_notes": "...",
  "artifacts": []
}

Detail fileCareerNavigator/applications/<application_id>.json, one per application:

{
  "schema": "application_detail_v1",
  "application_id": "app-<company-slug>-<role-keywords>",
  "application": "<company> — <role>",
  "company": "...",
  "role": "...",
  "stage_history": [
    {
      "stage": "...",
      "date": "YYYY-MM-DD",
      "notes": "...",
      "interview_type": "recruiter | hiring_manager | technical | panel | executive | final | null",
      "interviewers": [],
      "post_notes": null
    }
  ],
  "notes": [
    { "date": "YYYY-MM-DD", "text": "..." }
  ]
}

Contacts fileCareerNavigator/contacts/<company-slug>.json, one per company, shared by every application at that company:

{
  "company": "...",
  "contacts": [
    {
      "name": "...",
      "application": "<company> — <role>",
      "title": "...",
      "email": null,
      "linkedin": null,
      "relationship": "recruiter | hiring_manager | referral | internal_contact | other",
      "notes": "...",
      "interactions": [
        { "date": "YYYY-MM-DD", "type": "call | email | linkedin | in_person", "notes": "..." }
      ]
    }
  ],
  "contact_count": 0
}

offer and referral are omitted from new records unless relevant data is present. outcome defaults to "pending" on all new records. contacts_file and contact_count are omitted until the application has a contact. previous_ids appears on a row only after a rename.

Edit every one of these files by loading and re-dumping JSON programmatically (json.load / json.dump, indent=2, ensure_ascii=False), then reload to verify. Hand-editing raw JSON has corrupted files here before.


Read the full file on GitHub · 384 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. 5d ago First seen · 384 lines · 63 tokens per session scan A 7a3198e565d3

Subscribe to this mod's changes

track-application is a skill published in the GitHub repository tmargolis/career-navigator (13 stars, last pushed 7d ago), licensed Apache-2.0. It adds 63 tokens to every session and 4,451 once invoked, about $0.0003 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.