setup

setup is a skill for Claude Code from reggiechan74/JobOps. It costs 27 tokens per session (715 once invoked), scanned A, original, MIT.

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.

In plain words
What is it for?
Use it to create folders for services, prospects, proposals, pitches, rate cards, and landing pages, plus choose a contractor directory and default currency.
Why use it?
It prevents contractor work from being scattered across unrelated files and ensures the required workspace configuration exists before other tools run.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the jobops-ic plugin — 10 skills, 1 agent shipped together

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

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add reggiechan74/JobOps
Claude Code
/plugin install jobops-ic

Made for: Claude Code.

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

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 setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/reggiechan74/jobops/setup/github.svg)](https://agentmods.dev/skills/reggiechan74/jobops/setup)
Your own site
<a href="https://agentmods.dev/skills/reggiechan74/jobops/setup"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/setup/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 setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/reggiechan74/jobops/setup"><img src="https://agentmods.dev/badge/skills/reggiechan74/jobops/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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. 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.00027 $0.00715
Opus 5.5 $0.00011 $0.00286
Sonnet 5.5 $0.00005 $0.00143
Haiku 4.5 $0.00003 $0.00072

Measured 2mo ago against content hash 19a170eae025, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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:

  1. Contractor root directory — default ./Contractor. Validate the parent is writable.
  2. 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.

  1. 2mo 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 (26 stars, last pushed 5mo ago), licensed MIT. It adds 27 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5.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.

Related

setup compared with skills from other repositories

setup next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
setupreggiechan74/JobOpsSkill265mo agoMITA27Claude Code
imagegenopenai/codexSkill133kyesterdayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99kyesterdayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79k4d agoMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill313k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code