Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ojcp-org/ojcp --skill ojcp-job-searchgit clone --depth 1 https://github.com/ojcp-org/ojcpWrote 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/ojcp-org/ojcp/ojcp-job-search)<a href="https://agentmods.dev/skills/ojcp-org/ojcp/ojcp-job-search"><img src="https://agentmods.dev/badge/skills/ojcp-org/ojcp/ojcp-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/ojcp-org/ojcp/ojcp-job-search"><img src="https://agentmods.dev/badge/skills/ojcp-org/ojcp/ojcp-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.00061 | $0.01064 |
| Opus 5.5 | $0.00024 | $0.00426 |
| Sonnet 5.5 | $0.00012 | $0.00213 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
ojcp-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 today.
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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job search with OJCP
You are helping a person look for work. The Open Job Context Protocol (OJCP) is an open standard that job boards and employers use to publish openings for AI assistants. The public registry at https://ojcp.dev/api/registry lists the sources that support it. This skill searches all of them at once and returns real, current openings with links to apply.
Be clear with the person about coverage: these are the job sources that support OJCP so far, not every job on the internet.
1. Understand what they want
Before searching, make sure you know:
- The role: a job title, kind of work or skills ("data analyst", "night-shift RN", "React developer").
- Where: a city and state or region, or remote. Ask if it's unclear.
- Anything that rules a job out: minimum pay, full-time versus part-time, on-site versus hybrid versus remote.
Ask one short question if something important is missing. Don't interview them. Never ask for their name, email, phone, resume or other personal details to search: searching doesn't need them.
2. Search
Run the helper. It needs Node 18 or newer and has no dependencies:
node scripts/ojcp-search.mjs "data analyst" --city Chicago --state IL --limit 5
node scripts/ojcp-search.mjs "data analyst" --remote --limit 5
Options: --city, --state (two-letter US state or region), --country (ISO code like US), --remote (include remote roles), and --limit (results per source, default 5).
Only the search words and location filters are sent to the job sources. Nothing about the person is sent.
The output is JSON:
-
sources: each source that was searched and whether it answered. Mention a source that failed only if the person would care. -
jobs: one entry per opening, withsource,ojcp_id,title,employer,location,remote_policy,pay,posted,apply_urlandagent_can_apply.location_filter_ignored: truemeans that source couldn't filter by place, so check the location yourself and drop jobs that don't fit.
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.
- today First seen · 77 lines · 61 tokens per session scan A ce9d1152ffed
ojcp-job-search is a skill published in the GitHub repository ojcp-org/ojcp (105 stars, last pushed today), licensed Apache-2.0. It adds 61 tokens to every session and 1,064 once invoked, about $0.0002 per session on Opus 5.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-10-30.
Other skills, from other repositories
dt-config
El usuario elige cuánto contexto de reglas queda activo en esta máquina. El perfil no lleva nombre y no va a Git.
dt-calendar
Integración opcional de Calendar vía el MCP oficial del IDE. google-drive-dt está descontinuado.
dt-gmail
Integración opcional de Gmail vía el MCP oficial del IDE. google-drive-dt está descontinuado.
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
LifeOS memory, prior-session recall, and learning capture. USE WHEN capture this learning, document this learning, what did we learn recently, recent learnings, cortex, knowledge, knowledge base, search knowledge, what do we know about, archive, harvest, knowledge status, develop note, add to knowledge, add a people…