Borrowing it
Nothing to install: this file belongs to ncalavera/llm-job-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ncalavera/llm-job-pipeline/main/.claude/commands/jobs-update.mdgit clone --depth 1 https://github.com/ncalavera/llm-job-pipelineWrote 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/commands/ncalavera/llm-job-pipeline/jobs-update)<a href="https://agentmods.dev/commands/ncalavera/llm-job-pipeline/jobs-update"><img src="https://agentmods.dev/badge/commands/ncalavera/llm-job-pipeline/jobs-update/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/commands/ncalavera/llm-job-pipeline/jobs-update"><img src="https://agentmods.dev/badge/commands/ncalavera/llm-job-pipeline/jobs-update.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.00021 | $0.00728 |
| Opus 5 | $0.00010 | $0.00364 |
| Sonnet 5 | $0.00004 | $0.00146 |
| Haiku 4.5 | $0.00002 | $0.00073 |
Grade A, and why
jobs-update 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/jobs-update
Bring an existing install up to date safely. git pull alone is not enough:
new code can expect schema changes, so this command pulls and runs the
migration runner so the database matches the code.
Run this from the project root whenever you want the latest version.
Steps
-
Confirm the working tree is safe to update. Run
git status.- If there are uncommitted changes to tracked files, stop and show them. Ask
whether to commit, stash (
git stash), or abort. Never discard the user's changes automatically. .env,config/user_profile.mdand the localdata/database are gitignored, so a pull never touches them — reassure the user of that.
- If there are uncommitted changes to tracked files, stop and show them. Ask
whether to commit, stash (
-
Record the current version so the changelog is meaningful:
git rev-parse --short HEAD -
Pull the latest code (fast-forward only, so a diverged local branch fails loudly instead of producing a surprise merge):
git pull --ff-onlyIf it fails because the branch diverged, stop and report — let the user decide how to reconcile.
-
Refresh Python dependencies only if they changed since the old HEAD:
git diff --name-only <OLD_SHA> HEAD | grep -q requirements.txt && \ pip install -r requirements.txtIf
requirements.txtdid not change, skip this and say so. -
Apply pending database migrations. This works for both backends — it reads
SUPABASE_DB_URLfrom the environment to decide SQLite vs Supabase, and it takes an automatic backup (data/backups/) before touching anything:python3 scripts/migrate.pyShow its output. If it reports "Up to date", say there were no schema changes.
- If it exits with "ABORTED — destructive statements" (exit 2), STOP.
Do not re-run with
--allow-destructiveon the user's behalf. Show the listed migrations and let the user decide — that flag can drop or overwrite their data. - On SQLite, a failed migration auto-restores the database from the backup, so the data is never left half-migrated. Relay that if it happens.
- If it exits with "ABORTED — destructive statements" (exit 2), STOP.
Do not re-run with
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 530deeefb04c
- 12d ago First seen · 75 lines · 21 tokens per session scan A c093b1744531
jobs-update is a command published in the GitHub repository ncalavera/llm-job-pipeline (2 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 728 once invoked, about $0.0001 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 commands, from other repositories
init
Initialize configurations for Supabase local development.
database-setup
Use when a project needs to store data and has no database yet. Setting up Supabase, creating tables, writing queries, and connecting them to the frontend. Written for designers.
ingest
Manually add knowledge to the Weaviate store.
json.batch_delete
Delete multiple JSON documents or paths in one itemwise batch.
json.batch_get
Read multiple JSON values by document and path.
kv.batch_get
Read multiple KV values by key.