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.
git clone --depth 1 https://github.com/ishandutta2007/Awesome-AI-Job-HuntingWrote 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/ishandutta2007/awesome-ai-job-hunting/setup)<a href="https://agentmods.dev/commands/ishandutta2007/awesome-ai-job-hunting/setup"><img src="https://agentmods.dev/badge/commands/ishandutta2007/awesome-ai-job-hunting/setup/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/ishandutta2007/awesome-ai-job-hunting/setup"><img src="https://agentmods.dev/badge/commands/ishandutta2007/awesome-ai-job-hunting/setup.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.00000 | $0.05827 |
| Opus 5 | $0.00000 | $0.02913 |
| Sonnet 5 | $0.00000 | $0.01165 |
| Haiku 4.5 | $0.00000 | $0.00583 |
Grade A, and why
setup 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.
This is a copy
100% identical to setup — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 433 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/setup - Profile Onboarding
You are running the onboarding setup for the AI Job Search framework. Your goal is to collect the user's professional information and populate all profile files so the /apply workflow works out of the box.
There are three paths into setup. Step 0 picks the right one; all three converge on Step 3 (file generation) and Step 4 (confirmation).
Step 0: Welcome & Choose Path
If $ARGUMENTS contains --section <name>, skip directly to that section in Path C for an update-only flow. Do not run the path-selection prompt below.
Otherwise, first check where this working copy would publish to — before anything is
written, not after (the Step 4 privacy note fires only once every file is already on
disk, which is too late to inform the decision). Run git remote get-url origin; if the
command fails (no remote, or not a git checkout), skip this check silently. If there is
a GitHub origin, check it with gh repo view <owner/repo> --json visibility,isFork
when gh is available. If the origin is a public fork of the template — or its
visibility cannot be determined — warn now and wait:
Heads-up before we start: your
originpoints at<owner/repo>, which is a public GitHub fork. This setup writes your personal data (name, contact details, employment history, salary expectations) into tracked files, and anything you commit and push to that fork is visible to anyone. Two safe options: keep your profile commits local and never push them, or push to a private repository instead — SETUP.md section 8 has the two-minute private-remote recipe. Want to continue with the setup?
Wait for the user's confirmation before showing the path prompt. A private origin, no origin, or a non-fork remote needs no warning — continue silently.
Then, before greeting the user, scan the documents/ folder. Use Glob with documents/**/* and count files per subfolder (cv/, linkedin/, diplomas/, references/, applications/).
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 · 433 lines · 0 tokens per session scan A 70e1136a6fcc
setup is a command published in the GitHub repository ishandutta2007/Awesome-AI-Job-Hunting (3 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,827 tokens. A static security scan graded it A with 0 findings. It is 100% identical to setup, differing in 14 lines, and is treated as a copy.
Other commands, from other repositories
new-sdk-app
Create and setup a new Claude Agent SDK application.
review-issue
Review and respond to a GitHub issue.
analyze-codebase
Generate comprehensive analysis and documentation of entire codebase.
tdd
This outlines the development practices and principles we require you to follow. Don't start working on features until asked, this document is intended to get you into the right state of mind.
test
Focused on testing internal logic, not API endpoints.
review
Command "review" from Najeebullah3124/awesome-claude-universe, covering pr review, task 1: product manager review, task 2: developer review, task 3: quality engineer review and task 4: security engineer review.