What is setup-resume-workspace?

A workspace setup guide for Next Job Kit, a repository for managing resumes and job applications. It uses one candidate profile file to configure personal details, file paths, and career preferences.

Use it after cloning the repository, when personalizing paths and career details, repairing missing files, and checking the result with the project's validation command.

It finds missing or placeholder setup information while preserving resume, evidence, tracker, and submitted files that already contain real content.

How farrelfatah/nextjobkit configures Codex

Reuse

Borrowing it

Nothing to install: this file belongs to farrelfatah/nextjobkit. 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/farrelfatah/nextjobkit/main/.agents/skills/setup-resume-workspace/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/farrelfatah/nextjobkit

Made for: Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/farrelfatah/nextjobkit/setup-resume-workspace/github.svg)](https://agentmods.dev/skills/farrelfatah/nextjobkit/setup-resume-workspace)

Your own site

<a href="https://agentmods.dev/skills/farrelfatah/nextjobkit/setup-resume-workspace"><img src="https://agentmods.dev/badge/skills/farrelfatah/nextjobkit/setup-resume-workspace/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/farrelfatah/nextjobkit/setup-resume-workspace"><img src="https://agentmods.dev/badge/skills/farrelfatah/nextjobkit/setup-resume-workspace.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 515 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.

Model	Per session	Once invoked
Fable 5.1	$0.00056	$0.00515
Opus 5	$0.00028	$0.00258
Sonnet 5	$0.00011	$0.00103
Haiku 4.5	$0.00006	$0.00052

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

Security

Grade A, and why

setup-resume-workspace 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 10d 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.

.agents/skills/setup-resume-workspace/SKILL.md · 51 lines

How it starts

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

Set Up Resume Workspace

Create a usable evidence-first resume workspace while preserving anything the user already wrote.

Workflow

Read profile/candidate.md, README.md, and AGENTS.md.
Inspect the configured master resume, evidence file, and application tracker paths.
Identify blank profile fields, placeholder content such as Your Name or example.com, missing paths, and conflicting files.
Ask only for information needed to make the workspace usable. Prefer one focused round of five to seven questions.
Update profile/candidate.md as the sole user-facing configuration file.
Create a missing canonical file from the matching top-level templates/ file when available, then personalize its identity, headline, paths, and contact fields before calling setup complete.
Never replace a non-placeholder master resume, evidence file, tracker, or submitted artifact.
Run npm run validate and report any remaining setup gaps.

Candidate Profile Contract

Keep machine-readable scalar settings in YAML frontmatter and human decisions in the Markdown body.

Require these frontmatter keys:

schema_version
candidate_name
candidate_slug
resume_template
master_resume_path
resume_evidence_path
application_tracker_path

Treat contact links, location, positioning, work preferences, and claim boundaries as optional until the user needs them. Do not invent missing values.

Only accept a resume_template registered in export/templates.json. Do not silently substitute a template.

Safety Rules

Treat existing Markdown as user data.
Do not delete or rename submitted artifacts during setup.
Do not put secrets, government identifiers, private phone numbers, or unconfirmed compensation into tracked files.
Do not create multiple master resumes.
Preserve the configured paths during a compatibility migration.
Do not edit or regenerate .next-job-kit/ update metadata during setup; use the update CLI for version changes.

Read the full file on GitHub · 51 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

agents/openai.yaml 230 B

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.

10d ago First seen · 51 lines · 56 tokens per session scan A 819c93b652e0

Subscribe to this mod's changes

setup-resume-workspace is a skill published in the GitHub repository farrelfatah/nextjobkit (5 stars, last pushed 20d ago), licensed MIT. It adds 56 tokens to every session and 515 once invoked, about $0.0003 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.

Productivity

orbit-notion

Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…

nexu-io/open-design · 117 tokens

Cortex

Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…

danielmiessler/LifeOS · 196 tokens

pinchtab-mcp

Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.

pinchtab/pinchtab · 52 tokens

nextjobkit: Skill for Codex