A setup routine that adds independent-contractor folders, templates, and pricing settings to an existing JobOps workspace. It requires the base JobOps setup to be completed first.

Use it to create folders for services, prospects, proposals, pitches, rate cards, and landing pages, plus choose a contractor directory and default currency.

It prevents contractor work from being scattered across unrelated files and ensures the required workspace configuration exists before other tools run.

setup — Skill by reggiechan74

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 skills/reggiechan74/jobops/setup

Any agent

npx skills add reggiechan74/JobOps --skill setup

Clone the repo

git clone --depth 1 https://github.com/reggiechan74/JobOps

Made for: Claude Code, Codex.

Or install jobops-ic, the plugin that ships this one along with the rest of its 10 skills, 1 agent.

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

When invoked 715 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5	$0.00027	$0.00715
Opus 5	$0.00014	$0.00358
Sonnet 5	$0.00005	$0.00143
Haiku 4.5	$0.00003	$0.00072

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

Security

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 3d 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.

plugins/jobops-ic/skills/setup/SKILL.md · 115 lines

How it starts

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

JobOps IC Setup

This skill extends an existing JobOps workspace with the directories, templates, and config entries needed by the jobops-ic plugin. It does not create .jobops/config.json — it adds to the one created by /jobops:setup.

Step 1: Prerequisite check

Read .jobops/config.json.

If the file does not exist, stop with:

JOBOPS NOT CONFIGURED Run /jobops:setup first, then retry /jobops-ic:setup.

(The plugin dependencies field ensures jobops is installed alongside jobops-ic; this check catches the separate case of the user skipping the base setup.)

Step 2: Welcome

Print:

JobOps IC Setup

This extends your existing JobOps workspace with:

A contractor output tree (services, prospects, proposals, pitches, rate cards, landing pages)

The IC service-definition template

Currency preference for pricing outputs

Continue.

Step 3: Interview

Ask in order:

Contractor root directory — default ./Contractor. Validate the parent is writable.
Default currency — ISO 4217 code, enum: CAD | USD | EUR | GBP | AUD. Default CAD. Used by rate cards and proposals.

Step 4: Create directory tree

Run:

mkdir -p <contractor_root>/services \
         <contractor_root>/prospects \
         <contractor_root>/proposals \
         <contractor_root>/pitches \
         <contractor_root>/rate-cards \
         <contractor_root>/landing-pages

Report created vs exists.

Step 5: Template installation

Copy the IC service-definition schema into the workspace template tree:

cp ${CLAUDE_PLUGIN_ROOT}/templates/service_definition_schema.json .jobops/templates/default/

If the source file is missing, stop with a clear error. Do not silently skip.

Step 6: Extend `.jobops/config.json`

Read the existing config, add the following keys, and write it back atomically (write to .jobops/config.json.tmp, then mv):

directories.contractor_root = "<step-3 value>"
preferences.default_currency = "<step-3 value>"
templates.active.service_definition_schema = "default"

Read the full file on GitHub · 115 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.

3d ago First seen · 115 lines · 27 tokens per session scan A 19a170eae025

Subscribe to this mod's changes

setup is a skill published in the GitHub repository reggiechan74/JobOps (25 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 715 once invoked, about $0.0001 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-30.

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens