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/apply)<a href="https://agentmods.dev/skills/archugunov/pm-job-search/apply"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/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/archugunov/pm-job-search/apply"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/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.00184 | $0.03723 |
| Opus 5 | $0.00092 | $0.01861 |
| Sonnet 5 | $0.00037 | $0.00745 |
| Haiku 4.5 | $0.00018 | $0.00372 |
Grade A, and why
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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/apply — tailor a CV for a specific role
Single-purpose skill: produces a tailored CV file for one role at one company, by reading the user's master CV and rewriting it against the company's JD signals (from research-brief.md). Sits between /evaluate-position (which creates the company folder) and /interview-prep (which assumes an interview is already booked).
Voice: every prompt (multi-role disambiguation, Phase B clarifications, re-run choice) and the chat output follow ${CLAUDE_PLUGIN_ROOT}/TONE.md. Apply the low-effort-first principle — only ask the user when the answer changes the output.
Inputs
<Company>argument — required, e.g./apply Plaidor/apply "Plaid". Case-insensitive folder lookup againstuserdata/companies/. If no exact match, fuzzy-suggest:No 'Plad' folder. Did you mean Plaid? (y/n). If the company tracks multiple roles (subfolder layout), ask which:Plaid tracks 2 roles — pick: 1) senior-pm-consumer-credit, 2) lead-pm-risk-platform.userdata/cv.md(oruserdata/cv.txt) — the master CV, canonical source of truth for every factual claim in the tailored output. Skill cannot run without it.userdata/profile.md— read## Positioning,## Proof Points,## Moat,## Tone of Voice,## What NOT to Frame As.userdata/companies/<Co>/[<slug>/]meta.md— read frontmatter forposition,comp_band,location. Used for the tailored CV header context and the chat output.userdata/companies/<Co>/[<slug>/]research-brief.md— JD-grounded signals (Company snapshot, Why this fits, Open questions). Used to extract JD requirements for tailoring.
Optional flag:
--from-url <URL>— re-fetch the live JD via WebFetch instead of relying onresearch-brief.md. Use when the brief is stale or thin. If WebFetch fails or returns boilerplate, fall back toresearch-brief.mdand warn the user.
Missing-input handling (one-line errors, point to the fix, exit cleanly):
- No
userdata/cv.mdor.txt→ tell the user: "I don't have your CV yet — drop it intouserdata/as cv.md or cv.txt and I'll tailor from it." Exit. - No
userdata/companies/<Co>/folder → tell the user:No userdata/companies/<Co>/ — run /evaluate-position first.Exit. - No
research-brief.md(company was added manually rather than via/evaluate-position) → soft warning:No research-brief.md — tailoring will be looser. Continue?Default yes; if yes, proceed using onlymeta.md.positionto infer JD signals.
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 · 189 lines · 0 tokens per session scan A a99f50c100a4
apply is a skill published in the GitHub repository archugunov/pm-job-search (7 stars, last pushed 16d ago), licensed MIT. It adds 184 tokens to every session and 3,723 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
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.
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.
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.