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/integrations)<a href="https://agentmods.dev/skills/archugunov/pm-job-search/integrations"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/integrations/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/integrations"><img src="https://agentmods.dev/badge/skills/archugunov/pm-job-search/integrations.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.00135 | $0.02921 |
| Opus 5 | $0.00068 | $0.01460 |
| Sonnet 5 | $0.00027 | $0.00584 |
| Haiku 4.5 | $0.00014 | $0.00292 |
Grade A, and why
integrations 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 — 212 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/integrations — wire MCP-based integrations into the daily loop
Probes the user's installed MCPs for the three high-value integrations documented in ${CLAUDE_PLUGIN_ROOT}/INTEGRATIONS.md (Granola → /interview-analysis, Calendar → /today, Gmail → journal), reports what's available, walks the user through wiring each one in with minimal config, and saves the customized invocation patterns to userdata/integrations.md.
Voice: every prompt, status line, and saved invocation pattern follows ${CLAUDE_PLUGIN_ROOT}/TONE.md. Apply the low-effort-first principle — probe before asking, offer defaults, accept skip on every question, stop the moment value is delivered.
The other three integrations in INTEGRATIONS.md (Notion, Playwright, Slack) stay manual-setup — the user reads INTEGRATIONS.md and applies them directly. This skill covers the three that plug into the daily/weekly loop.
Inputs
No required arguments. Optional flag:
--refresh— re-probe and rewriteuserdata/integrations.mdeven if it already exists. Default behaviour: ifuserdata/integrations.mdexists, show what's wired and ask whether to refresh, add new integrations only, or exit.
Flow
- Probe each of the three MCPs.
- Report detection results in a compact table.
- Wire each available integration via a per-integration sub-flow (1-2 questions max).
- Write
userdata/integrations.mdwith the customized invocation patterns. - Close with 2-4 example invocations the user can copy-paste.
Probe step
Probe order: Granola → Calendar → Gmail. Each probe attempts a safe, read-only call. The skill must NOT ask the user "do you have ?" before probing — detect first.
Mechanic — how to enumerate MCP tools. MCP tools surface as mcp__<server>__<tool> in the deferred-tool list. To check if a server is wired, use ToolSearch with a pattern query (e.g. ToolSearch query="mcp__granola" or ToolSearch query="mcp__gcal") to enumerate matching tools. If matches surface, the server is installed; if zero matches, treat as not_installed. For Calendar and Gmail where naming varies, try multiple patterns in sequence (see per-integration sections below).
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 · 212 lines · 135 tokens per session scan A 277d0faba648
integrations is a skill published in the GitHub repository archugunov/pm-job-search (7 stars, last pushed 16d ago), licensed MIT. It adds 135 tokens to every session and 2,921 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
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.