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 archugunov/pm-job-search/plugin install pm-job-searchWrote 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/archugunov/pm-job-search/job-search)<a href="https://agentmods.dev/skills/archugunov/pm-job-search/job-search"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/job-search/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/archugunov/pm-job-search/job-search"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/job-search.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.00181 | $0.06101 |
| Opus 5 | $0.00090 | $0.03050 |
| Sonnet 5 | $0.00036 | $0.01220 |
| Haiku 4.5 | $0.00018 | $0.00610 |
Grade A, and why
job-search 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 12d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/job-search — three-phase discovery and monitoring sweep
Architecture lifted from the predecessor workflow with two changes: storage is md files (not Notion); Playwright is optional (not required). Three phases: pre-flight, parallel work, final merge.
Voice: every prompt (search-query review, recheck-failure handling) and the chat summary follow ${CLAUDE_PLUGIN_ROOT}/TONE.md. Phase 2 auto-files every surviving candidate (no pick step, no preview table). Run summaries and failure messages follow TONE.md — plain prose, no fenced blocks.
Inputs
userdata/profile.md—target_titles,target_industries,geography,hard_filters,tier_thresholds.- All
userdata/companies/*/meta.mdANDuserdata/companies/*/*/meta.md— needed for the exclusion sets AND for the monitoring watchlist. - Optional flags:
--no-parallel— run Recheck and Discovery sequentially in the main conversation, no subagents (slower but easier to debug).--discovery-only/--recheck-only— skip the other phase.--companies <Co1,Co2>— when combined with--recheck-only, scope the recheck.--with-playwright— use Playwright MCP for link-liveness verification in Phase 2. If the MCP isn't installed, fall back gracefully and notelink_verified: false.
If userdata/profile.md is missing, tell the user to run /setup first; do not proceed.
Phase 0 — Pre-flight (always sequential, in main conversation)
Produce two artefacts on disk for the parallel agents to consume, plus resolve the companies-of-interest question with the user before anything is dispatched:
A. /tmp/pmjs-exclusion.json
Build the exclusion set from two sources so a role stays suppressed even after its company folder is deleted:
- Existing meta.md. Walk both glob patterns and collect every role's
(company, position)pair plus every non-emptylink. - The seen-ledger at
userdata/outputs/seen-roles.jsonl(append-only, one JSON object per line). If it exists, read every line and fold itsstrict_key/base_key/url_keyinto the set. This is what remembers a role the user archived by deleting its folder rather than marking itnot_interested. If the file is absent, skip — first run creates it in Phase 2.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 285 lines · 0 tokens per session scan A 0583e362798f
job-search is a skill published in the GitHub repository archugunov/pm-job-search (7 stars, last pushed 17d ago), licensed MIT. It adds 181 tokens to every session and 6,101 once invoked, about $0.0009 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 skills, from other repositories
chapter-writing
This skill should be used when the user asks to "write a chapter", "next chapter", "chapter outline", "draft chapter", "continue the story", "write a scene", "outline a chapter", or wants to write prose for a story project.
story-init
This skill should be used when the user asks to "start a new story", "initialize a story project", "create a story", "new book", "set up a story", or wants to begin a new fiction writing project from scratch.
revision-continuity
This skill should be used when the user asks to revise a chapter, edit prose, continuity check, find inconsistencies, audit character state, check timeline consistency, line edit, developmental edit, polish a draft, or prepare existing story material for the next revision pass.
story-maintenance
This skill should be used when the user asks to validate, reindex, repair registries, check links, check continuity, count words, summarize a story project, import an existing manuscript, export a manuscript, run the story CLI, or perform deterministic maintenance on a Story Skills markdown project.
alive:demo
Generate a believable, lived-in ALIVE world from a free-text persona description (custom path) or a deterministic sandbox preset. Routes the create/list/activate/deactivate/delete/status surface and orchestrates the 5-stage subagent generation pipeline.
alive:system-upgrade
Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.