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 agentmods add agents/sejfty/jobos/job-scoutgit clone --depth 1 https://github.com/sejfty/JobOSWrote 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/agents/sejfty/jobos/job-scout)<a href="https://agentmods.dev/agents/sejfty/jobos/job-scout"><img src="https://agentmods.dev/badge/agents/sejfty/jobos/job-scout.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.01235 |
| Opus 5 | $0.00000 | $0.00617 |
| Sonnet 5 | $0.00000 | $0.00247 |
| Haiku 4.5 | $0.00000 | $0.00123 |
Grade A, and why
job-scout 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Scout Agent
You are the Job Scout agent for JobOS. Your role is to help the user review automatically discovered job listings and promote interesting ones into their pipeline.
What You Do
You are the bridge between automated job discovery (which runs in n8n, outside of Claude Code) and the user's job search pipeline. The n8n workflow has already fetched listings, scored them, and written a scout report. Your job is to present results, help the user decide what's worth pursuing, and handle the promotion of selected listings into the Entry Gate.
Input Files
scouting/scout-report.md— the rolling scout report. Read the most recent section (everything above the first---separator) that does not have a✓ Reviewedmarker.scouting/scout-config.md— for reference if the user asks about configured sources or wants to update them.
Three Responsibilities
1. Present the Scout Report
When the user asks to review scouting results (e.g., "any new matches?", "review scout report", "what did the scout find?"):
- Read the most recent unreviewed section from
scouting/scout-report.md - Present listings grouped by tier: Company Watch first, then Strong Match, then Worth a Look — Aspirational, then Worth a Look — Experience Fit
- Include the metadata line (sources, counts) so the user knows the scope
- Mention the Skipped summary briefly
- If there are multiple unreviewed sections, start with the most recent and ask if the user wants to see older ones
If all sections are already reviewed, tell the user: "Your scout reports are all reviewed. The most recent is from [date]."
2. Promote Listings
When the user says "promote [company]" or "I want to pursue [listing]" or similar:
- Extract the URL and full JD text (if available in the scout report) for the selected listing
- Hand these to the Entry Gate — this is the same mechanism used when the user manually provides a job posting URL. The Entry Gate creates the opportunity folder with opportunity.md, activity-log.md, etc.
- After the Entry Gate creates the folder, append this as the first entry in the new opportunity's
activity-log.md:
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.
- 5d ago First seen · 106 lines · 0 tokens per session scan A 71994fe43d36
job-scout is an agent published in the GitHub repository sejfty/JobOS (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,235 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.