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/Miracle-Aligner/job-search-hqnpx agentmods add skills/miracle-aligner/job-search-hq/recheck-statusesWrote 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/miracle-aligner/job-search-hq/recheck-statuses)<a href="https://agentmods.dev/skills/miracle-aligner/job-search-hq/recheck-statuses"><img src="https://agentmods.dev/badge/skills/miracle-aligner/job-search-hq/recheck-statuses/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/miracle-aligner/job-search-hq/recheck-statuses"><img src="https://agentmods.dev/badge/skills/miracle-aligner/job-search-hq/recheck-statuses.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.00121 | $0.01040 |
| Opus 5.5 | $0.00048 | $0.00416 |
| Sonnet 5.5 | $0.00024 | $0.00208 |
| Haiku 4.5 | $0.00012 | $0.00104 |
Grade A, and why
recheck-statuses 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
recheck-statuses
Flow
- Segment entries into sweepable vs pipeline-locked.
- Probe each sweepable URL (cheapest tool first).
- Apply
closedto dead postings, preserving priorstatusDetail. - Report +
python3 scripts/validate.py→python3 scripts/bake.py.
Segmentation
Statuses are about the candidate's pipeline, not the posting's liveness — they don't undo each other. Only flip rows that are currently:
to_apply— not yet engagedwatch— already on holdclosed— already dead (re-verify; postings sometimes reopen)
Skip rows in any of these stages, even if their URL looks dead:
applied,hr_screen,tech_interview,final,offer,rejected
The reasoning: a posting going dark doesn't undo a real conversation. If the user wants to reopen one of these, they'll say so explicitly.
Probing
| Primary URL host | Tool | "Closed" signal |
|---|---|---|
jobs.dou.ua/companies/... |
WebFetch |
HTTP 404 · вакансія неактивна / закрита · page redirects to /companies/<co>/vacancies/ |
djinni.co/jobs/<id>-<slug>/ |
WebFetch, Chrome fallback |
404 · Вакансія неактуальна · архівована |
linkedin.com/jobs/view/... |
Claude in Chrome (auth) | "No longer accepting applications" · 404; if not logged in, mark unknown, don't guess |
| Google Docs / Other | WebFetch |
Title + role text present → alive; else unknown, ask the user |
Throttling: DOU 429s under parallel load. Cap concurrent WebFetchs at ~3. If you hit two 429s
in a row, back off 60s and mark the rest unknown instead of looping.
A slug change (same role, new vacancy id) reads as deleted here. If the user has the new
URL, they'll re-add via /add-vacancy.
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 First seen · 100 lines · 121 tokens per session scan A dc8c82469a0d
recheck-statuses is a skill published in the GitHub repository Miracle-Aligner/job-search-hq (1 stars, last pushed 4mo ago), licensed MIT. It adds 121 tokens to every session and 1,040 once invoked, about $0.0005 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-31.
Other skills, from other repositories
solve-captcha
Solve a CAPTCHA on the current browser tab - free checkbox/text paths first, then a configured token service for image challenges. Returns solved or unsolved for the caller to fall back.
ww-upload-cover-letter
Upload a PDF cover letter from the coverletter/ folder (typically coverletter/Company-coverletter.pdf produced by ww-write-cover-letter) into a required WaterlooWorks Cover Letter document slot during the Full-Cycle Service Submit Application workflow. Use when a WaterlooWorks application package requires Cover…
myb-p-chatbots
Build, edit, repair and verify MyBusiness MyChat chatbots using BOTH MyBusiness MCP and the actual browser editor. Use whenever a user asks to create a chatbot, build a WhatsApp bot, design a conversation flow, add an AI agent to a bot, fix broken chatbot nodes/options/layout, or turn a valid database graph into a…
ww-login
Restore a WaterlooWorks Chrome session when Codex is viewing or applying to WaterlooWorks jobs and lands on recoverable logged-out states such as notLoggedIn.htm, WaterlooWorks - Not Logged In, the WaterlooWorks home page, or waterloo.htm?action=login. Use before asking the user to log in; stop and ask only when…
test-site
Tests a deployed, activated Power Pages site at runtime using browser-based navigation, page crawling, and API request verification via Playwright. Use when the user wants to test, verify, or smoke-test their deployed site.
preview-screens
Use when the user wants to preview generated screens in a browser without starting Metro / a simulator — for example after /create-mobile-app finishes or after /edit-app regenerates a screen.