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-profile.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-profile)<a href="https://agentmods.dev/commands/ncalavera/llm-job-pipeline/jobs-profile"><img src="https://agentmods.dev/badge/commands/ncalavera/llm-job-pipeline/jobs-profile/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-profile"><img src="https://agentmods.dev/badge/commands/ncalavera/llm-job-pipeline/jobs-profile.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.00031 | $0.02258 |
| Opus 5 | $0.00015 | $0.01129 |
| Sonnet 5 | $0.00006 | $0.00452 |
| Haiku 4.5 | $0.00003 | $0.00226 |
Grade A, and why
jobs-profile 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 12d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/jobs-profile
Manage config/user_profile.md — the single source of truth for scoring AND
filtering. Three modes selected by the first argument:
| Invocation | What it does |
|---|---|
/jobs-profile (no arg) |
Print a profile summary + active HARD filters |
/jobs-profile rules |
Edit geo policy (ban_regions, keep_countries, ban_us_only, …) + exclude_title_keywords in ## HARD_FILTERS |
/jobs-profile edit |
Broader edits — seniority, target roles, exclude patterns, geography |
Profile creation (first-time) happens on the onboarding page (docs/index.html)
or automatically when you first run /jobs-new. This command never creates the
profile from scratch — it only reads or edits an existing one.
Mode: view (no arg)
Step 1 — Locate the profile
Check whether config/user_profile.md exists.
-
File present — proceed to Step 2.
-
File absent — print:
No profile found — showing example
config/user_profile.mddoes not exist yet. The output below comes fromconfig/user_profile.example.mdso you can see what a completed profile looks like. To create your real profile, complete the onboarding wizard on the landing page (docs/index.html) or run/jobs-new(first run detects an empty database and walks you through setup).Then read
config/user_profile.example.mdand proceed — but treat every displayed value as illustrative, not real.
Step 2 — Print the profile summary
Read the profile and summarise in plain language:
- Seniority target (from
## SENIORITYor equivalent section) - Target roles / titles (from
## TARGET_ROLES) - Geography preferences (from
## GEOGRAPHY) - Exclude patterns (from
## EXCLUDE_PATTERNS— soft score penalty) - Hard filters — run the snippet below and read the result back conversationally:
python3 -c "
import sys; sys.path.insert(0, 'scripts')
from hard_filters import load_hard_filters
hf = load_hard_filters()
fmt = lambda v: ', '.join(v) if v else '(none)'
print('Banned regions:', fmt(hf['ban_regions']))
print('Kept (whitelist):', fmt(hf['keep_countries']))
print('Banned countries:', fmt(hf['ban_countries'] + hf['exclude_countries']))
print('Drop US/Canada-only roles:', 'yes' if hf['ban_us_only'] else 'no')
print('On-site no-penalty regions:', fmt(hf['onsite_ok_regions']), '| penalty:', hf['onsite_penalty'])
print('Title words dropped:', fmt(hf['exclude_title_keywords']))
"
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.
- 12d ago First seen · 232 lines · 31 tokens per session scan A 158a8788aa14
jobs-profile is a command published in the GitHub repository ncalavera/llm-job-pipeline (2 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 2,258 once invoked, about $0.0002 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.