reset

A reset command for a job-search workspace that can clear candidate information, uploaded documents, or both after confirmation.

In plain words
What is it for?
Use it to reset profile data, remove files from the documents folder, or reset both parts of the job-search setup.
Why use it?
It lets you start the job-search process over while keeping the framework itself intact.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/madslorentzen/ai-job-search/reset
Clone the repo
git clone --depth 1 https://github.com/MadsLorentzen/ai-job-search

Made for: Claude Code.

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 2,638 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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 $0.00000 $0.02638
Opus 5 $0.00000 $0.01319
Sonnet 5 $0.00000 $0.00528
Haiku 4.5 $0.00000 $0.00264

Measured 2d ago against content hash 8f10f9e650ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

reset scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf documents/applications/*/
Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • reset — 100% identical, 0 lines differ
.claude/commands/reset.md · 276 lines

How it starts

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

/reset - Reset Candidate Profile Data

You are resetting parts of the job search framework back to a blank state so the user can start fresh with /setup.

This command is destructive. Nothing is deleted until the user explicitly confirms. Follow these steps exactly in order.


Step 0: Parse Scope from Arguments

Check $ARGUMENTS for a scope keyword:

  • profile — clears candidate profile data from skill files only
  • documents — deletes user-provided files from the documents/ folder only
  • all — both of the above

If $ARGUMENTS is empty or does not contain a recognized scope keyword, ask:

What would you like to reset?

  • profile — Clears candidate data from the skill files (profile, behavioral, STAR examples, profile statements, personalized evaluation criteria, search queries). The framework structure, scoring framework, and writing rules are preserved. Use this to re-run /setup from scratch.

  • documents — Deletes all files you've placed in the documents/ folder (CV PDFs, LinkedIn export, diplomas, references, pasted job postings, past applications). The folder structure and README.md are preserved.

  • all — Both of the above.

Reply with profile, documents, or all.

Wait for the user's response before continuing.


Step 1: Show Exactly What Will Be Cleared

Before doing anything, show the user precisely what will be wiped.

If scope includes profile:

Read the current state of these files and report whether each has content or is already empty:

  • .claude/skills/job-application-assistant/01-candidate-profile.md
  • .claude/skills/job-application-assistant/02-behavioral-profile.md
  • .claude/skills/job-application-assistant/04-job-evaluation.md (personalized match areas, career goals, and life-situation constraints only — the scoring framework is preserved)
  • .claude/skills/job-application-assistant/05-cv-templates.md (profile statements section only — framework structure is preserved)
  • .claude/skills/job-application-assistant/07-interview-prep.md (STAR examples and STAR candidates sections only — framework structure is preserved)
  • .claude/skills/job-scraper/search-queries.md (role titles, domain keywords, and location terms only — query structure is preserved)

Read the full file on GitHub · 276 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. 2d ago First seen · 276 lines · 0 tokens per session scan C 8f10f9e650ff

Subscribe to this mod's changes

reset is a command published in the GitHub repository MadsLorentzen/ai-job-search (39,400 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,638 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.