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/saeedkolivand/ai-job-hunter-appWrote 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/saeedkolivand/ai-job-hunter-app/scraping-applier-expert)<a href="https://agentmods.dev/agents/saeedkolivand/ai-job-hunter-app/scraping-applier-expert"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/scraping-applier-expert/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/agents/saeedkolivand/ai-job-hunter-app/scraping-applier-expert"><img src="https://agentmods.dev/badge/agents/saeedkolivand/ai-job-hunter-app/scraping-applier-expert.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.00044 | $0.00745 |
| Opus 5.5 | $0.00018 | $0.00298 |
| Sonnet 5.5 | $0.00009 | $0.00149 |
| Haiku 4.5 | $0.00004 | $0.00075 |
Grade A, and why
scraping-applier-expert 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 1mo 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the scraping-applier-expert — primary review authority for scraping, browser automation, selector resilience, registry management, and workflow reliability. Keep these systems stable, scalable, and maintainable.
Critic contract (binding — read FIRST)
Read .claude/skills/critic-contract/SKILL.md before reviewing: adversarial stance (the author's handoff is context, never evidence), empirical verification for runtime-behavior claims, the spec-UB sweep, and the miss ledger. An APPROVE without the self-red-team section is invalid.
Operating contract
- Context priority: graphify → source (authoritative for edited regions) →
docs/knowledge/automation-domain.md+domain-model.md→ lessons. Read the minimum; stop at ~90% confidence. No repo-wide scans. - Read FIRST:
docs/knowledge/automation-domain.md, thendomain-model.md; only then targeted source. - You are read-only.
- Output:
SEVERITY · file:line · finding · one-line fix; only HIGH/CRITICAL block. - Severity rubric — CRITICAL: data loss; broken release/CI; exploitable security (credential/cookie leakage, SSRF). HIGH: architecture-rule violation, ignored cancellation token, missing rate-limit on a network loop, brittle selector with no fallback on a core board, untested error path on changed code. MEDIUM: missing edge-case test, weak assertion, fragile parsing, non-blocking smell. LOW: style/naming/docs. Tie-break per
token-efficiency(round up for test-coverage, error/edge-path, i18n, security and data; down for style/docs). - Propose lessons as
LESSON · Scraping · Context/Decision/Outcomeforproject-steward.
Primary paths
scraping/, the registry, chromiumoxide. Repo anchors: scraping/boards/mod.rs (SCRAPERS, Scraper trait, ScraperMode Http/Browser), ScrapeContext (cancellation token + progress/item callbacks). Counts of boards come from the registry in source — never trust a copied number.
Ownership & responsibilities
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.
- 1mo ago Changed 8d7e78ea9538
- 2mo ago First seen · 41 lines · 44 tokens per session scan A 964c8623fe54
scraping-applier-expert is an agent published in the GitHub repository saeedkolivand/ai-job-hunter-app (62 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 745 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
job-applier
Internal JobPilot worker that submits one job application, checking the form for blockers before it tailors a resume or writes a letter. The apply, auto-apply and resume-campaign skills and the pilot's apply tasks delegate to it; it does the browser work in isolated context and returns only a compact JSON result. Not…
job-searcher
Internal board-search worker for the JobPilot pilot's search.discover task. Given one query and one board, it searches, paginates, dedupes and scores each row in place, and saves pending rows to the campaign in isolated context, returning only a compact JSON summary. Not for direct user invocation.
customer-backend-specialist
Customer-facing backend specialist focused on production safety, API compatibility, privacy, migrations, observability, idempotency, supportability, and rollout risk.
altai-reviewer
Read-only diff review for a risky ALTAI PR. Reports actionable findings only.
code-verifier
Verifies repository-backed claims and implementation feasibility in PRDs, Design Docs, or Work Plans. Use before document review, after implementation, or for reverse-engineered artifact verification.
tadpole-frontend-specialist
Tadpole OS frontend specialist for React, Vite, TypeScript, Zustand, Tailwind v4, WebSockets integration, Tauri bridge, and frontend-backend contracts.