Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add aksheyw/career-command-center-template/plugin install career-ccWrote 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.
[](https://agentmods.dev/skills/aksheyw/career-command-center-template/followup)<a href="https://agentmods.dev/skills/aksheyw/career-command-center-template/followup"><img src="https://agentmods.dev/badge/skills/aksheyw/career-command-center-template/followup/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.
<a href="https://agentmods.dev/skills/aksheyw/career-command-center-template/followup"><img src="https://agentmods.dev/badge/skills/aksheyw/career-command-center-template/followup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00042 | $0.01862 |
| Opus 5 | $0.00021 | $0.00931 |
| Sonnet 5 | $0.00008 | $0.00372 |
| Haiku 4.5 | $0.00004 | $0.00186 |
Grade A, and why
followup 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are managing follow-up cadence for the user's active applications. Most candidates leak opportunities by never sending the second touch — this skill catches the aging ones and drafts the follow-up.
Cadence model adapted from the followup mode of santifer/career-ops (MIT), rebuilt to read this plugin's tracker and to write in the user's own voice.
STEP 1: Load the data
Read ${CLAUDE_PLUGIN_ROOT}/references/applications.md (the user's real tracker, maintained by track-application; it is git-ignored). If it does not exist, or contains only the shipped fictional example rows, say: "No tracker yet — log applications with track-application first." Stop. (The committed applications.example.md is a schema reference only — never treat its rows as real.)
Today's date is the system date. Use it for all aging math. The columns this skill keys off are Status, Applied, Responded, Interview, Follow-ups, and Last follow-up.
STEP 2: Apply cadence rules
Assign urgency per row using the status and the relevant date column. "Days since" always uses the Last follow-up date if present, otherwise the driving date named below. For the interview rows, "thank-you already logged" means a follow-up dated on or after the Interview date exists (Last follow-up ≥ Interview date) — that is the dated exit out of the thank-you window.
| Status | Driving date | Rule | Becomes... |
|---|---|---|---|
responded |
Responded | reply within 24h of their response | URGENT — actionable until you log a follow-up dated on/after the Responded date |
interview, Interview date in the FUTURE |
Interview | the interview hasn't happened — nothing to send yet | upcoming — not actionable |
interview, Interview date today or within the last ~1 day, no thank-you logged yet (Last follow-up empty or before the Interview date) |
Interview | send a thank-you within 24h of the interview | URGENT (thank-you) — exits the moment you log a follow-up dated on/after the Interview date, or ages out of the 24h window into the next row |
interview, Interview date more than ~1 and up to ~30 days past, no thank-you logged yet |
Interview | the 24h thank-you window has closed — send the (now-late) thank-you / status-check | OVERDUE (late thank-you) — no longer URGENT |
interview, thank-you already logged, ~5-7 business days since the last touch, no reply |
Last follow-up | send one status-check | OVERDUE (status-check) |
interview, Interview date more than ~30 days past with no progression (no reply, and either no thank-you ever or gone quiet since the last touch) |
Interview, else Last follow-up | it has gone cold — stop chasing | COLD (stale) — suggest closing |
applied / screening |
Last follow-up, else Applied | past 7 days with no follow-up | OVERDUE |
| any status, Follow-ups ≥ 2 | — | don't draft a third | COLD — suggest closing |
| within a window above, or an upcoming interview waiting to happen | — | on track | waiting / upcoming |
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.
- 10d ago First seen · 87 lines · 42 tokens per session scan A 749d88a4e2f0
followup is a skill published in the GitHub repository aksheyw/career-command-center-template (1 stars, last pushed 11d ago), licensed MIT. It adds 42 tokens to every session and 1,862 once invoked, about $0.0002 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.
Other skills, from other repositories
interviewing
Use when the user gets an interview invitation, moves into an interview process, wants to track interview stages, capture post-interview notes, draft follow-up messages, or update an application to interviewing.
get-started
Use when the user is new to Job Hunt Skills and wants to see what it does or set up their workspace — including "I'm new to Job Hunt Skills", "help me get started", "set me up", "first time using this", "here's my resume, tailor it for this job", "can you look at my resume", pasting a resume and a job posting…
kochab
Kochab, a personalized resume-based job-search assistant that runs a recurring scan and everything downstream of it. Use when the user wants to start or run a job search, shares a resume, or says "set up my job scan," "find roles that fit my resume," or "what should I apply to." Also use to tailor a resume, draft a…
Job Description Analyzer
Analyze job postings, calculate match scores, identify gaps, and create application strategy.
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.
Application Form Filler
Fill out job application form fields with context-aware, tailored answers drawn from the candidate's CV and the job description.