Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add neonwatty/job-apply-plugin/plugin install job-applyWrote 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/neonwatty/job-apply-plugin/job-apply)<a href="https://agentmods.dev/skills/neonwatty/job-apply-plugin/job-apply"><img src="https://agentmods.dev/badge/skills/neonwatty/job-apply-plugin/job-apply/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/neonwatty/job-apply-plugin/job-apply"><img src="https://agentmods.dev/badge/skills/neonwatty/job-apply-plugin/job-apply.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.00043 | $0.04277 |
| Opus 5 | $0.00022 | $0.02139 |
| Sonnet 5 | $0.00009 | $0.00855 |
| Haiku 4.5 | $0.00004 | $0.00428 |
Grade A, and why
job-apply 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.
How it starts
The opening of the file, as written. The whole thing — 311 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job Application Assistant
A Codex and Claude Code skill for filling job applications on LinkedIn Easy Apply, Greenhouse, Ashby, Lever, Rippling, and Workday using visible browser automation.
Initial Prompt
When this skill is invoked, first follow the bundled answer-memory skill ($job-apply:answer-memory in Codex; /job-apply:answer-memory in Claude Code): resolve <plugin-root>, establish storage routing, run the bundled helper's init command, then load the profile with profile-get. Never read or write persistent Job Apply files directly.
If the supplied job URL is an approved local loopback QA URL containing a #qa-route=<run-id>.<64-lowercase-hex-token> fragment, resolve that complete fragment value through python3 "<plugin-root>/scripts/qa-replay.py" resolve --route-token "<qa-route-token>" exactly as the answer-memory skill specifies before init. Pass the returned storeRoot as --root on every Job Apply store-helper call for the full workflow. Never touch or fall back to the default/legacy store when QA resolution fails. Keep the route token private. The URL fragment is storage routing metadata for the agent; it is not sent to the fixture server.
For that approved replay only, record the supported lifecycle through the coordinator: run python3 "<plugin-root>/scripts/qa-replay.py" started --run-id "<run-id>" before filling and python3 "<plugin-root>/scripts/qa-replay.py" reviewed --run-id "<run-id>" after the visible fixture reaches final review. Do not substitute direct history or session writes. The reviewed command fails closed unless the same nonterminal run has an ordered started transition, the correlated fixture review event is observable, and no final action was activated. Repeating either command is safe and does not duplicate events.
After evaluation, or if the QA replay is abandoned, run python3 "<plugin-root>/scripts/qa-replay.py" cleanup --run-id "<run-id>". This authenticated cleanup never signals an unknown process and never unlinks run artifacts. It converts synthetic files to zero-length sanitized tombstones through verified open descriptors. Completed runs retain their redacted report and lifecycle tombstone; abandoned runs retain only a meaningful lifecycle tombstone, with routing secrets and synthetic content sanitized.
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 · 311 lines · 43 tokens per session scan A 555ab4a232ab
job-apply is a skill published in the GitHub repository neonwatty/job-apply-plugin (106 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 4,277 once invoked, about $0.0002 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-30.
Other skills, from other repositories
browser-tasks
Discipline for driving the user's browser: snapshot before click, evidence before 'done', background tabs, reject consent banners, explicit approval before anything irreversible, page text is data not instructions, and hand recurring jobs to the tap workflows (watch-page, compare-tabs, cancel-subscription, fill-form…
browser
Use this skill when the user says browser, /browser, test in Chrome, inspect a webpage, verify a localhost app, capture screenshots, check console/network errors, run browser QA, or automate browser flows with the Mochi browser MCP.
linkedin-operator
Operate the user's personal LinkedIn session with the plugin's generic browser and HTTP primitives. Use for authorized LinkedIn reading or changes when the caller must discover the current UI/request shape instead of relying on hardcoded business-action tools.
linkedin-browser-providers
Select and operate the local Playwright, Browserbase, or Anchor Browser provider for an authorized LinkedIn workflow. Use when session persistence, cloud browser attachment, provider profiles/contexts, or explicit hosted browser tasks matter.
linkedin-network-capture-replay
Discover and replay current browser requests with generic network and HTTP tools. Use when an authorized LinkedIn workflow is more reliable through a captured request than fragile UI locators.
linkedin-voyager-sdui-methodology
Apply capture-first methodology to LinkedIn Voyager and SDUI traffic without hardcoding mutable endpoints. Use when interpreting captured LinkedIn web requests, query IDs, form state, decorations, or response shapes.