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-network)<a href="https://agentmods.dev/commands/cyn-zhang/job-radar/job-network"><img src="https://agentmods.dev/badge/commands/cyn-zhang/job-radar/job-network/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-network"><img src="https://agentmods.dev/badge/commands/cyn-zhang/job-radar/job-network.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.00012 | $0.00234 |
| Opus 5 | $0.00006 | $0.00117 |
| Sonnet 5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
job-network 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
Run JobRadar alumni networking. Load config from config.yaml, then follow Module 11 in SKILL.md.
Usage examples:
- /job-network --spike — validate whether LinkedIn alumni search is extractable before building automation
- /job-network --map — build alumni company distribution and save networking/alumni_map.json
- /job-network --list — show saved alumni grouped by company
- /job-network --list Atlassian — show saved alumni at one company
- /job-network --reach Atlassian — generate personalised outreach drafts for alumni at Atlassian
- /job-network --prep "Sarah Chen" — prepare coffee chat questions
Tracking:
- Alumni map lives in networking/alumni_map.json
- Long-term outreach status lives in applications/tracker.json under networking[]
- When the user drafts, sends, gets a reply, schedules a chat, or receives a referral, update both stores
Safety rules:
- Never send LinkedIn messages automatically.
- User must review and manually send every message.
- Store alumni data only in networking/ (gitignored).
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 · 23 lines · 12 tokens per session scan A 099d2f50794d
job-network is a command published in the GitHub repository cyn-zhang/job-radar (3 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 234 once invoked, about $0.0001 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
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
enum-udp
UDP scan + service follow-up — top ports first, full sweep only when justified.
review
Submit a story for verification (In Progress → In Review, no PR yet).
standup
Alias of /board — the async sprint snapshot.
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.