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/discoverWrote 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/discover)<a href="https://agentmods.dev/skills/palashjain95/jobhunter/discover"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/discover/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/discover"><img src="https://agentmods.dev/badge/skills/palashjain95/jobhunter/discover.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.00086 | $0.01567 |
| Opus 5 | $0.00043 | $0.00783 |
| Sonnet 5 | $0.00017 | $0.00313 |
| Haiku 4.5 | $0.00009 | $0.00157 |
Grade A, and why
discover 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/discover
If you see unfamiliar
~~placeholders, see CONNECTORS.md.
Usage
/discover
/discover product manager at fintech startups
/discover senior PM roles in NYC
/discover <URL to job board or company careers page>
How It Works
┌─────────────────────────────────────────────────────────┐
│ DISCOVER │
├─────────────────────────────────────────────────────────┤
│ Phase 1: Build queries from profile │
│ - Expand target titles to adjacent roles │
│ - Map seniority level to search terms │
│ │
│ Phase 2: Search across sources │
│ - Target company careers pages (if companies listed) │
│ - Web search (LinkedIn, job boards, career pages) │
│ - Industry-specific boards │
│ │
│ Phase 3: Evaluate and fetch JDs │
│ - Quick fit score (High / Medium / Low) │
│ - Fetch full JD text when possible │
│ - Flag logistics (visa, relocation, start date) │
│ │
│ Phase 4: Triage and present │
│ - Deduplicate, rank by fit, group by company │
│ - Separate: Role Matches vs Hidden Gems │
└─────────────────────────────────────────────────────────┘
Detailed search strategies are in references/search-strategies.md. Load it for
platform-specific query patterns and title expansion tables.
Inputs
- Candidate profile from knowledge/profile.md (target roles, companies, location, situation)
- Optional: specific company, role type, job board URL, or search criteria from user
- If pipeline-data.md exists: check for existing contacts that could be referral paths
Produce
1. Role Matches
For each discovered role:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 164 lines · 86 tokens per session scan A ee6c17dd0262
discover is a skill published in the GitHub repository palashjain95/jobhunter (2 stars, last pushed 5mo ago), licensed MIT. It adds 86 tokens to every session and 1,567 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
meta-tags-optimizer
Optimize title tags, meta descriptions, Open Graph, and Twitter cards for maximum click-through rate. Generates multiple A/B test variations with character counting and SERP preview. Use when asked to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "fix my meta tags", "social media…
google-ads-audit
Google Ads account audit and business context setup. Run this first — it gathers business information, analyzes account health, and saves context that all other ads skills reuse. Trigger on "audit my ads", "ads audit", "set up my ads", "onboard", "account overview", "how's my account", "ads health check", "what should…
sxo
Search Experience Optimization (SXO) — the bridge between SEO and UX/CRO. Audits the full journey from the SERP click to the on-page goal: SERP click-through factors (title/meta/rich results that win the click), then post-click experience signals that keep users and drive conversions — above-the-fold relevance and…
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.