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 agentmods add commands/treymorgan/jobsearch-apply-mcp/gmail-syncgit clone --depth 1 https://github.com/treymorgan/jobsearch-apply-mcpWhat 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 | $0.00000 | $0.03709 |
| Opus 5 | $0.00000 | $0.01854 |
| Sonnet 5 | $0.00000 | $0.00742 |
| Haiku 4.5 | $0.00000 | $0.00371 |
Grade A, and why
gmail-sync 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 today.
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 gmail-sync — 0 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 — 193 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/gmail-sync - Sync Application Status from Gmail
You are scanning the user's Gmail for status signals on tracked job applications (interview invites, assessment links, offers, rejections) and, once approved, writing the detected changes into job_search_tracker.csv and documents/applications/<company>_<role>/outcome.md - the same two places /outcome writes to, in the same schema.
Unlike /outcome (which asks the user what happened), /gmail-sync classifies real emails on its own - but it never writes on its own. Every classified change is presented as a batch before anything touches the tracker or outcome.md, and only proceeds once the user approves it (approving the whole batch at once is fine; writing first and flagging it after is not). Because a wrong write silently corrupts application history that /setup later calibrates from, every proposed change must cite its source email and every uncertain case must be surfaced instead of guessed. Never treat this command's job as "notice something in an inbox" - it is "propose a correct, sourced line for a permanent record, and write it only once the user says yes."
Follow these steps in order.
Step 0: Prerequisites
Confirm the Gmail MCP tools (mcp__claude_ai_Gmail__*) are available. If not, tell the user to connect the Gmail integration (claude.ai Settings → Connectors → Gmail) and stop - do not attempt this via Bash, IMAP, or any other channel.
Step 1: Parse Input
$ARGUMENTS may contain:
- Nothing → default lookback (see Step 3)
- A company name, e.g.
/gmail-sync acme→ scope the search to that one tracked application since <YYYY-MM-DD>→ override the lookback start date for this run only (does not change the persisted state file)
Step 2: Load State
- Read
job_search_tracker.csv. If it does not exist, tell the user there is nothing to sync against yet (suggest/outcomeor/applyfirst) and stop. Do not create it here -/gmail-syncnever originates new applications, only updates existing ones. - Read
gmail_sync/state.json(create if missing:{"last_sync": null, "processed_message_ids": []}). - Build the set of open applications: tracker rows whose
statusis not Final (per the Tracker status vocabulary in/outcome). For each, derive its archive folderdocuments/applications/<company>_<role>/by the Subfolder naming rule indocuments/README.mdand check whetheroutcome.mdexists there. Reuse this exact derived path for any write in Step 7a.
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.
- today First seen · 193 lines · 0 tokens per session scan A 613f9817df69
gmail-sync is a command published in the GitHub repository treymorgan/jobsearch-apply-mcp (0 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,709 tokens. A static security scan graded it A with 0 findings. It is 100% identical to gmail-sync, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
compile-today
Compiles today's CVs, runs the ATS check, and archives (doesn't touch the tracker).
interview-prep
Read workflows/interview-prep.md, profile/candidate.yaml, rules/interview-roteiro.md + rules/job-evaluation.md (to re-fetch the job description) and rules/cv-rules.md (for the overlap logic reused when picking the project). Execute the steps described there for the company received in $ARGUMENTS.
apply-batch
Read workflows/apply-batch.md, profile/candidate.yaml and rules/cv-rules.md.
confirm
Read workflows/confirm.md and profile/candidate.yaml (the tracker.backend field decides whether registration goes to Notion, CSV, or none). Execute the steps described there for the indices/names received in $ARGUMENTS.
daily
Read workflows/daily.md and profile/candidate.yaml (run python3 scripts/validateprofile.py first to validate). Execute the steps described there, using rules/job-evaluation.md for the fit score.
quick-eval
Quick job evaluation. Paste a JD and get a score plus one-paragraph summary. Faster than a full evaluate. Use when someone says 'quick eval', 'quick score', or 'just give me a number'.