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 bendrucker/claude --skill jobgit clone --depth 1 https://github.com/bendrucker/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/bendrucker/claude/job)<a href="https://agentmods.dev/skills/bendrucker/claude/job"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/job/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/bendrucker/claude/job"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/job.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.02622 |
| Opus 5 | $0.00041 | $0.01311 |
| Sonnet 5 | $0.00016 | $0.00524 |
| Haiku 4.5 | $0.00008 | $0.00262 |
Grade A, and why
job 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 2d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Job
Run a daily work routine: gather state read-only, present one prioritized brief, then execute confirmed bulk actions through installed skills.
Config
!cat ~/.config/claude-job-skill/config.json 2>/dev/null || echo CONFIG_MISSING
If the output above is CONFIG_MISSING and the requested mode is not setup, run the interview in references/setup.md first, then continue into the requested mode.
Mode
Requested mode: $0. Local time: !date "+%A %H:%M".
start: read references/start.mdend: read references/end.mdsetup: read references/setup.md
With no argument, suggest a mode from the local time above: before the midpoint of the configured working hours (about 13:00 by default) suggests start, after suggests end. On a weekend, suggest nothing and ask. Confirm the suggestion with AskUserQuestion before proceeding.
Arguments beyond the mode are a focus hint ($ARGUMENTS). Weight the brief toward what they name.
Delegation
This skill never names platforms. The config declares which version-control platform, issue tracker, worktree tool, messaging platform, email account, and optional personal capture inbox the user works with. For each task, find the installed skill covering the configured tool's task and load it for mechanics, falling back to the configured CLI or MCP directly. Stay read-only until the user confirms actions.
Platforms, hostnames, and usernames come only from the config or the user, never from this skill.
Brief, then act
Both modes follow this contract.
Gather
Read-only first. The sources are independent (review queue, own PRs, tracker, messaging inbox, email inbox), so dispatch parallel read-only sub-agents and merge their results. Merge on shared identifiers: when items from different sources name the same issue or MR, they are one piece of work and become one brief entry carrying every source's state. The join is the orchestrator's job, keyed on the cross-references each sub-agent returns.
What ships with it
3 files 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.
- 2d ago Changed 0da1221c5fd5
- 5d ago First seen · 131 lines · 82 tokens per session scan A 0a9498297a2c
job is a skill published in the GitHub repository bendrucker/claude (16 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 2,622 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
recipe-plan
Create work plan from design document and obtain plan approval.
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…
alive:bundle
Create, share, and graduate bundles — the unit of focused work within a walnut. Manages the full bundle lifecycle from creation through sharing to graduation.
recruit-init
Uma habilidade que prepara um espaço de trabalho para recrutamento, com pastas, documentos de referência, registros e instruções para agentes de programação. Ela verifica dependências como Node.js, ferramentas de vagas e, opcionalmente, o Feishu.
status
Read every application.yaml in the workspace and report the state of the search — the ranked queue, what is waiting on you, what has gone quiet, and the regression of the pipeline's own predictions against actual outcomes. Writes the calibration findings back into jobsearch.md and preferences.yaml.
skill-task-management
Manage tasks with Claude Code native tools — use to track TODOs, delegate work, and monitor progress.