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/evaluate-position)<a href="https://agentmods.dev/skills/archugunov/pm-job-search/evaluate-position"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/evaluate-position/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/evaluate-position"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/evaluate-position.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.00137 | $0.04220 |
| Opus 5 | $0.00068 | $0.02110 |
| Sonnet 5 | $0.00027 | $0.00844 |
| Haiku 4.5 | $0.00014 | $0.00422 |
Grade A, and why
evaluate-position 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 — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/evaluate-position — score a job posting against the tier rubric
Single-role discovery. Takes one posting (URL or pasted JD), produces a tier score and a research brief, files them under userdata/companies/<Co>/ per the §I.4 folder layout. Idempotent against re-evaluation of the same role; never duplicates an existing (company, position) pair.
Voice: every prompt (hard-filter bypass, score override, re-evaluation choice) and the chat output / written brief follow ${CLAUDE_PLUGIN_ROOT}/TONE.md. Apply the low-effort-first principle — accept defaults where they work, only ask the user when input changes the outcome.
Inputs
- The user's input — one of:
- A URL (the user typed
/evaluate-position https://example.com/jobs/123or similar). Use the WebFetch tool to retrieve the page content. If WebFetch fails or returns boilerplate (login wall, JS-only render), tell the user and ask them to paste the JD instead. - Pasted JD text (the user pasted the posting body). Use as-is.
- Nothing — prompt:
Paste the job description, or give me a URL to fetch.
- A URL (the user typed
userdata/profile.md— read frontmatter fortier_weights,tier_thresholds,company_shape_adjustment,target_industries,target_titles,hard_filters, and the## Positioningbody. Skill cannot run without profile.md — if missing, tell the user to run/setupfirst.- All existing
userdata/companies/*/meta.mdANDuserdata/companies/*/*/meta.md— needed for dedup detection and folder-layout decisions.
Extract from the JD
Parse and pin down, in order:
- Company name. Prefer the JD's own statement ("About "); fall back to URL domain if pasted text omits it. Use the company's canonical name (e.g.
Stripe, notstripe.com). Title-case. - Position title (the role name as posted, e.g.
Senior PM, Consumer Credit). Keep the company's exact phrasing — do NOT normalize to your own ladder. This is whatmeta.mdstores aspositionand what the dedup rule keys on. - Location — on-site city, hybrid days, or remote-region.
- Reports-to (if disclosed) and team-size (if disclosed).
- Compensation band (if disclosed). Most JDs don't disclose; note "not disclosed" when absent.
- Notable signals: funding stage (Series A/B/etc.), team size at the company (LinkedIn count or "About us" mention), founder-led status, PLG/sales-led, scope (IC vs people-management).
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 · 243 lines · 137 tokens per session scan A ca1e7d5462a5
evaluate-position is a skill published in the GitHub repository archugunov/pm-job-search (7 stars, last pushed 17d ago), licensed MIT. It adds 137 tokens to every session and 4,220 once invoked, about $0.0007 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.