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.
npx skills add palashjain95/jobhunter --skill offer-analysisgit clone --depth 1 https://github.com/palashjain95/jobhunterWrote 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/offer-analysis)<a href="https://agentmods.dev/skills/palashjain95/jobhunter/offer-analysis"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/offer-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/offer-analysis"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/offer-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.00073 | $0.01192 |
| Opus 5 | $0.00036 | $0.00596 |
| Sonnet 5 | $0.00015 | $0.00238 |
| Haiku 4.5 | $0.00007 | $0.00119 |
Grade A, and why
offer-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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/offer-analysis
Usage
/offer-analysis <paste offer details>
/offer-analysis I got an offer from Stripe: $180k base, 50k RSUs...
/offer-analysis compare Stripe vs Google offers
How It Works
┌─────────────────────────────────────────────────────────┐
│ OFFER ANALYSIS │
├─────────────────────────────────────────────────────────┤
│ SINGLE OFFER → Evaluate │
│ - Break down total comp (Y1, Y2, 4-year) │
│ - Compare to market data │
│ - Recommend: accept / negotiate / walk │
│ │
│ MULTIPLE OFFERS → Compare │
│ - Side-by-side table + weighted scoring │
│ - Best/risk/ceiling analysis per offer │
│ - "What you'll regret" for each option │
└─────────────────────────────────────────────────────────┘
Inputs
- Offer details (from user — base, equity, sign-on, benefits, etc.)
- Company and role (one or more)
- knowledge/profile.md — seniority context
- knowledge/negotiation/strategy.md — comp preferences and priorities
- If available: output/[company]/offer-analysis.md for prior evaluations
Part 1: Single Offer Evaluation
1. Offer Breakdown
| Component | Amount | Notes |
|---|---|---|
| Base salary | ||
| Equity/RSUs | Vesting schedule | |
| Sign-on bonus | ||
| Annual bonus | Target % | |
| Benefits | Health, 401k match, etc. | |
| PTO | ||
| Remote/hybrid |
Total comp: Year 1 | Year 2 | 4-year total
2. Market Comparison
How this compares to market for role/level/location. Cite sources (levels.fyi, Glassdoor, Blind). Verdict: Below / At / Above Market.
3. Candidate Alignment
How this maps to priorities from knowledge/negotiation/strategy.md. Does it meet the walk-away threshold?
4. What's Negotiable
What to push on, what to accept, in what order.
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.
- 9d ago First seen · 148 lines · 73 tokens per session scan A 92d09d4c8e75
offer-analysis is a skill published in the GitHub repository palashjain95/jobhunter (2 stars, last pushed 5mo ago), licensed MIT. It adds 73 tokens to every session and 1,192 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
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.
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".
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…