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/fit-analysisWrote 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/fit-analysis)<a href="https://agentmods.dev/skills/palashjain95/jobhunter/fit-analysis"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/fit-analysis/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/fit-analysis"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/fit-analysis.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.00081 | $0.01106 |
| Opus 5 | $0.00041 | $0.00553 |
| Sonnet 5 | $0.00016 | $0.00221 |
| Haiku 4.5 | $0.00008 | $0.00111 |
Grade A, and why
fit-analysis 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/fit-analysis
If you see unfamiliar
~~placeholders, see CONNECTORS.md.
Usage
/fit-analysis <paste JD, drop file, or provide URL>
How It Works
┌─────────────────────────────────────────────────────────┐
│ FIT ANALYSIS │
├─────────────────────────────────────────────────────────┤
│ Step 1: FIT SCORE (should you apply?) │
│ - Score 0-100 across 4 dimensions │
│ - Must-have / nice-to-have requirements check │
│ - Strengths + gaps + recommendation │
│ │
│ Step 2: RESUME OPTIMIZATION (if applying) │
│ - ATS compatibility check │
│ - Keyword gap analysis │
│ - Rewritten bullet points with missing keywords │
│ - Summary/headline rewrite for this role │
└─────────────────────────────────────────────────────────┘
Inputs
- Job description (file, URL, or pasted text)
- Candidate resume from knowledge/resume/
- Candidate profile from knowledge/profile.md
If URL provided, fetch the full JD text first.
Produce
Part 1: Fit Score
1. Overall Fit Score (0-100)
Score across 4 dimensions (0-25 each):
- Technical skills match
- Domain experience match
- Seniority/scope match
- Culture/values signals
2. Requirements Check
List every must-have and nice-to-have from the JD. For each: Met / Partial / Missing — with specific evidence from the resume.
3. Strengths + Gaps
- Top strengths to highlight for THIS role
- Top gaps to address — and how to mitigate each
4. Recommendation
Strong Apply / Apply / Apply with Modifications / Skip — with one sentence of reasoning.
Part 2: Resume Optimization (if recommendation is Apply or above)
If recommendation is Skip, skip this section entirely.
5. ATS Compatibility Check
Flag formatting issues, missing section headers, or problematic elements (tables, columns, graphics).
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 · 151 lines · 81 tokens per session scan A 5df92ecd98fc
fit-analysis is a skill published in the GitHub repository palashjain95/jobhunter (2 stars, last pushed 5mo ago), licensed MIT. It adds 81 tokens to every session and 1,106 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.
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…