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-digest.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-digest)<a href="https://agentmods.dev/commands/ncalavera/llm-job-pipeline/jobs-digest"><img src="https://agentmods.dev/badge/commands/ncalavera/llm-job-pipeline/jobs-digest/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-digest"><img src="https://agentmods.dev/badge/commands/ncalavera/llm-job-pipeline/jobs-digest.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.00013 | $0.00313 |
| Opus 5 | $0.00006 | $0.00156 |
| Sonnet 5 | $0.00003 | $0.00063 |
| Haiku 4.5 | $0.00001 | $0.00031 |
Grade A, and why
jobs-digest 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.
What it actually says
/jobs-digest
The daily driver sends one short message: the Inbox vacancy count and its link. Only preparations matching the current posting and profile count. Run failures remain visible; preparation queues belong to Health. Keep, Pass, Undo, and optional reasons live in the dashboard.
Preview or send
python3 scripts/telegram_digest.py send --dry-run
python3 scripts/telegram_digest.py send
Preview does not send messages or update delivery state. A successful send advances
last_digest_at; a failed send leaves it unchanged for retry. The summary does not
mark individual vacancies as delivered.
Configuration comes from the existing environment: TELEGRAM_BOT_TOKEN,
TELEGRAM_CHAT_ID, the database connection, and DASHBOARD_BASE_URL (or the
dashboard_base_url setting). Change the shared bot configuration to route all
JobSearch notifications together, including nightly failures and mail notifications.
Optional legacy reports
Only when explicitly requested:
python3 scripts/telegram_digest.py send --details --dry-run
python3 scripts/telegram_digest.py send --details
python3 scripts/telegram_digest.py alert --dry-run
--details retains scored vacancy lists and their delivery claims. alert checks
expiring scored roles. Neither is required for daily screening. The digest has no
response buttons or polling process; decisions are made in the dashboard.
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 · -19 lines · -5 tokens per session 00c7f600c8c6
- 12d ago First seen · 60 lines · 18 tokens per session scan A f4d373fa7ba5
jobs-digest is a command published in the GitHub repository ncalavera/llm-job-pipeline (2 stars, last pushed 3d ago), licensed MIT. It adds 13 tokens to every session and 313 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.