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.
git clone --depth 1 https://github.com/palashjain95/jobhunternpx agentmods add skills/palashjain95/jobhunter/follow-upWrote 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/palashjain95/jobhunter/follow-up)<a href="https://agentmods.dev/skills/palashjain95/jobhunter/follow-up"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/follow-up/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/palashjain95/jobhunter/follow-up"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/follow-up.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.00104 | $0.01239 |
| Opus 5 | $0.00052 | $0.00620 |
| Sonnet 5 | $0.00021 | $0.00248 |
| Haiku 4.5 | $0.00010 | $0.00124 |
Grade A, and why
follow-up 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/follow-up
If you see unfamiliar
~~placeholders, see CONNECTORS.md.
Usage
/follow-up <company name>
/follow-up I haven't heard back from Stripe
/follow-up I got rejected from Google
Two modes: nudge stalled applications, or process a rejection gracefully.
Inputs
- Which company/role
- Whether this is a FOLLOW-UP (no response) or REJECTION (got a no)
- pipeline-data.md — current status and timeline
- knowledge/profile.md — candidate context
- knowledge/frameworks/writing-framework.md — communication style
- For rejection: what they said, how far you got
- If available: output/[company]/fit-analysis.md, interview-prep.md
Mode 1: Follow-Up (stalled application)
Timing Rules
- After applying, no response: follow up after 5-7 business days
- After no response to first follow-up: one more nudge after ~5 days
- After two follow-ups with no response: stop. Application is cold.
Produce
Follow-Up Message (concise, ~75-100 words)
- Lead with something real — new context, relevant news, additional insight
- Restate interest briefly
- Make it easy to respond (yes/no question or clear next step)
Two versions: Email (with subject line) + LinkedIn message (shorter).
Context Note — why this follow-up is appropriate now, what risk exists, when to give up.
Mode 2: Handle Rejection
Ask the user (if details not provided)
One at a time:
- "Which company and role?"
- "What stage were you at? (applied / screened / interviewed / final)"
- "What did they say?"
Produce
1. What This Rejection Tells You
- Stage signal (what rejection at this stage typically means)
- Pattern check (is this repeated? what's emerging?)
- What was in your control vs not
2. Gracious Response (send within 24-48 hours, concise ~50-75 words)
- Thank them genuinely, express continued interest, leave the door open
- DO NOT ask why you were rejected or push back
Two versions: Email + LinkedIn message.
3. Lessons Extracted Stage-specific analysis: what to improve for next time.
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.
- 11d ago First seen · 161 lines · 104 tokens per session scan A ccdadc400737
follow-up is a skill published in the GitHub repository palashjain95/jobhunter (2 stars, last pushed 5mo ago), licensed MIT. It adds 104 tokens to every session and 1,239 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.
Other skills, from other repositories
i-have-adhd
Shape output for a reader with ADHD: lead with the next action, number multi-step work, restate state across turns, suppress tangents, give specific time estimates, make wins visible. Invoke with /i-have-adhd; stays on until "stop adhd mode".
mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
phx-mix-compression
Reduce mix output noise (5-15% token savings) by installing rtk filters that compress mix test/credo/dialyzer/compile output before it reaches Claude. Use when long mix output floods context.
quick
Implement small Phoenix changes without planning — add validations, update routes, fix components, create migrations. Use for single-file edits under 50 lines.
phx-freeze
Apply an advisory edit scope in this session. Use for read-only or directory-scoped work; no enforcement hook is installed.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…