ai-job-search-cn: Command for Claude Code

.claude/commands/outcome.md

outcome is a command for Claude Code from cypggs/ai-job-search-cn. It costs 0 tokens per session (1,774 once invoked), scanned A, original, MIT.

A command for recording updates and final results for job applications in a job-search tracker and an archive for each application.

In plain words
What is it for?
Use it to mark interviews, completed stages, offers, rejections, no responses, or hiring decisions for a selected company and role.
Why use it?
It keeps application outcomes in the places the job-search framework already uses, so statuses, duplicate checks, and later profile reviews stay up to date.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is cypggs/ai-job-search-cn's own configuration. It tells Claude Code how to work on ai-job-search-cn itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything ai-job-search-cn configures →

Reuse

Borrowing it

Nothing to install: this file belongs to cypggs/ai-job-search-cn. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/cypggs/ai-job-search-cn/master/.claude/commands/outcome.md
Clone the repo
git clone --depth 1 https://github.com/cypggs/ai-job-search-cn

Made for: Claude Code.

Wrote 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.

agentmods badge for outcome

README.md
[![agentmods](https://agentmods.dev/badge/commands/cypggs/ai-job-search-cn/outcome/github.svg)](https://agentmods.dev/commands/cypggs/ai-job-search-cn/outcome)
Your own site
<a href="https://agentmods.dev/commands/cypggs/ai-job-search-cn/outcome"><img src="https://agentmods.dev/badge/commands/cypggs/ai-job-search-cn/outcome/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.

agentmods 80×15 button for outcome

Your own site · 80×15
<a href="https://agentmods.dev/commands/cypggs/ai-job-search-cn/outcome"><img src="https://agentmods.dev/badge/commands/cypggs/ai-job-search-cn/outcome.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,774 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01774
Opus 5 $0.00000 $0.00887
Sonnet 5 $0.00000 $0.00355
Haiku 4.5 $0.00000 $0.00177

Measured 12d ago against content hash 3bb8fdb5c4f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

outcome 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.

.claude/commands/outcome.md · 125 lines

How it starts

The opening of the file, as written. The whole thing — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/outcome - Record the Result of an Application

You are recording what happened to a job application: progress updates (interview invitations, stages completed, offers) and final resolutions (hired, rejected, no response). The data lands in two places the framework already reads but nothing systematically writes:

  • job_search_tracker.csv - the status column that /scrape and /rank use for dedup and exclusion
  • documents/applications/<company>_<role>/ - the per-application archive (posting, submitted drafts, outcome.md) that /setup Path A mines to calibrate 04-job-evaluation.md and surface STAR candidates

/outcome writes the data; /setup interprets it. This command never edits the evaluation framework or profile files itself.

Follow these steps in order.


Step 0: Parse Input

$ARGUMENTS may contain:

  • Nothing → list open applications and ask which one to update
  • A company name (optionally with a role), e.g. /outcome acme or /outcome acme ml engineer → target that application

Step 1: Load State and Identify the Application

  1. Read job_search_tracker.csv. If it does not exist, create it with the standard header:
    date,company,sector,role,role_type,channel,status,contact_person,fit_rating,notes,cv_file,cover_letter_file,source
    
  2. With an argument: match rows case-insensitively on company (and role, if given). One match → proceed. Several → list them and ask. None → the application was made outside the workflow; collect company, role, date applied, channel, and posting URL from the user and add a tracker row.
  3. Without an argument: list all rows whose status is not final (not hired / rejected / no response / withdrawn / offer declined) as a numbered table (company, role, date applied, current status) and ask which to update. If every row is resolved, say so and stop.
  4. Derive the archive folder name: documents/applications/<company>_<role>/ - lowercase, underscores for spaces (the convention documented in documents/README.md). Check whether the folder and an outcome.md already exist - if so, you are updating, not creating.

Read the full file on GitHub · 125 lines

Changes

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.

  1. 12d ago First seen · 125 lines · 0 tokens per session scan A 3bb8fdb5c4f3

Subscribe to this mod's changes

outcome is a command published in the GitHub repository cypggs/ai-job-search-cn (63 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,774 tokens. 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-30.