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.
git clone --depth 1 https://github.com/cyn-zhang/job-radarWrote 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/commands/cyn-zhang/job-radar/job-status)<a href="https://agentmods.dev/commands/cyn-zhang/job-radar/job-status"><img src="https://agentmods.dev/badge/commands/cyn-zhang/job-radar/job-status/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/commands/cyn-zhang/job-radar/job-status"><img src="https://agentmods.dev/badge/commands/cyn-zhang/job-radar/job-status.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.00004 | $0.00139 |
| Opus 5 | $0.00002 | $0.00069 |
| Sonnet 5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
job-status 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.
What it actually says
Show a summary of all active job applications using JobRadar. Load config from config.yaml, then follow Module 10 in SKILL.md.
Read applications/tracker.json (source of truth) and present:
- A status summary table (grouped: Offers → Interviews → Applied → Watchlist → Needs Attention → Closed)
- Upcoming deadlines flagged 🔴 (within 7 days)
- Stale applications flagged ⚠️ (no status change in 14+ days)
- Networking summary if tracker.json has networking[] records
- A one-line recommended next action
Pass "closed" to expand the closed list: /job-status closed
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 · 14 lines · 4 tokens per session scan A 8e044eb91ff1
job-status is a command published in the GitHub repository cyn-zhang/job-radar (3 stars, last pushed 3mo ago), licensed MIT. It adds 4 tokens to every session and 139 once invoked, about $0.0000 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 commands, from other repositories
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
firm
Convene your standing AI staff — memos on every beat, a board session without you, minutes with dissent preserved.
ship-a-feature
Workflow recipe — take a feature idea from fuzzy brief to launch plan by chaining 5 skills.
ship-an-mcp-server
Workflow recipe — make your product agent-usable by chaining 4 skills, spec to pricing.
rescue-an-account
Workflow recipe — diagnose an at-risk customer and build the full save play through to renewal by chaining 4 skills.
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.