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 DmytroRybka/jobctl-claude --skill jobctlgit clone --depth 1 https://github.com/DmytroRybka/jobctl-claudeWrote 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/dmytrorybka/jobctl-claude/jobctl)<a href="https://agentmods.dev/skills/dmytrorybka/jobctl-claude/jobctl"><img src="https://agentmods.dev/badge/skills/dmytrorybka/jobctl-claude/jobctl/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/dmytrorybka/jobctl-claude/jobctl"><img src="https://agentmods.dev/badge/skills/dmytrorybka/jobctl-claude/jobctl.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.00067 | $0.00780 |
| Opus 5 | $0.00034 | $0.00390 |
| Sonnet 5 | $0.00013 | $0.00156 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
jobctl 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 — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.
jobctl — job application tracking
jobctl is the user's job-application tracker. You are the primary writer: whenever the user mentions anything about their job search, record it via the jobctl MCP tools without being asked. The user reads and plans in the dashboard at https://app.jobctl.app.
Core rules
- Record immediately. "I applied to Bosch" →
add_application(orupdate_applicationtoappliedif the card exists). Don't ask permission for routine tracking; do tell the user what you recorded. - One card per company+role. Before adding,
list_applicationsto check for an existing card; the API also returnsduplicateswarnings — if present, update the existing card instead. - Keep the timeline honest. Recruiter calls, sent messages, feedback →
add_note. Status changes are logged automatically. - Save your analysis — it is product data, not chat.
- Vacancy fit assessment ("why this role fits, gaps, level/salary advice, process notes") →
match_notesfield (markdown, ≤20 KB) on add/update. - Company research (business, culture, comp bands, risks, interview process, sources) →
attach_analysis(markdown, ≤100 KB, replaces previous).
- Vacancy fit assessment ("why this role fits, gaps, level/salary advice, process notes") →
- Always set
next_action+next_action_dueso the user's "Needs your attention" list stays useful. Clear it when done, set the next one.
Statuses
started_apply → waiting_referral (parked on a referral ask, not yet submitted) → applied → waiting → interview_1 → interview_2 → offer → accepted.
Terminal: rejected, no_response, withdrawn, on_hold. archived = old campaigns only (excluded from analytics).
Setting applied auto-stamps applied_at with today when empty.
Raw one-liners
add_application({raw: "..."}) parses: "Company, Role, prio A|B|C, due <date>, remote|hybrid|onsite, via <source>, https://…, in <location>, applied <date>". Dates are DD/MM or natural ("friday"). Salaries are integer EUR (e.g. 120000).
Interviews
log_interview with scheduled_at (ISO, timezone!), attendees [{name, url?}] (LinkedIn profiles), links [{label?, url}] (prep material, meeting link), status planned|done, recap after it happened. Max 10 per application. The soonest upcoming one drives the card's next-interview date.
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 · 40 lines · 67 tokens per session scan A dfb9f9258c9f
jobctl is a skill published in the GitHub repository DmytroRybka/jobctl-claude (0 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 780 once invoked, about $0.0003 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
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
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.