A setup and migration procedure for the claude-harness plugin in a project. It creates or upgrades project files, memory folders, ignore rules, and configuration.

Use it to initialize the harness, migrate a version 2 project, configure project memory, or remove obsolete command and hook copies.

It removes the manual work of identifying whether a project needs a fresh installation, an upgrade, or cleanup of old files.

setup — Skill for Claude Code and Codex by panayiotism: A setup and migration procedure for the claude-harness plugin…

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/panayiotism/claude-harness/setup

Any agent

npx skills add panayiotism/claude-harness --skill setup

Clone the repo

git clone --depth 1 https://github.com/panayiotism/claude-harness

Made for: Claude Code, Codex.

Or install claude-harness, the plugin that ships this one along with the rest of its 6 skills, 1 agent, 8 hooks.

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/panayiotism/claude-harness/setup.svg)](https://agentmods.dev/skills/panayiotism/claude-harness/setup)

Your own site

<a href="https://agentmods.dev/skills/panayiotism/claude-harness/setup"><img src="https://agentmods.dev/badge/skills/panayiotism/claude-harness/setup.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 1,107 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.00043	$0.01107
Opus 5	$0.00022	$0.00553
Sonnet 5	$0.00009	$0.00221
Haiku 4.5	$0.00004	$0.00111

Measured 5d ago against content hash e134f1b23f1e, 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 5d 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.

skills/setup/SKILL.md · 90 lines

How it starts

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

Setup - Initialize or Upgrade Claude Harness

Initialize or upgrade claude-harness in the current project directory.

Auto-Detection

This command automatically detects what needs to be done:

Fresh install: Creates v3.0 structure from scratch
v2.x upgrade: Migrates existing files to v3.0 memory architecture
Cleanup: Removes legacy command copies from .claude/commands/ (commands are now served from plugin cache)

Note: Commands and hooks are served from the plugin cache. setup.sh only initializes project-level state (memory directories, CLAUDE.md, .gitignore, migrations).

Phase 0: Run setup.sh (Handles ALL Cases)

setup.sh handles fresh installs, v2.x migrations, and cleanup in a single script. Always run it.

Steps:

Find the plugin root path from the session context (look for "Plugin Root:" in the session start context)
Run: bash {plugin-root}/setup.sh
- Fresh install: Creates v3.0 structure, .gitignore patterns, CLAUDE.md
- v2.x migration: Detects legacy files, migrates to v3.0 structure, then creates missing files
- Cleanup: Removes stale command copies from .claude/commands/ and legacy hooks
- Existing project files are NEVER overwritten (skipped automatically)
- .gitignore patterns are added if missing
Report what was created vs what was skipped
Skip Phase 3 -- setup.sh handles it

Fallback: If the plugin root path is not available in the session context, fall through to Phase 1 -> Phase 4 (manual setup).

Plugin updates: Run claude plugin update claude-harness to update the plugin itself.

Phase 3: Update Project .gitignore (FALLBACK -- only if setup.sh unavailable)

CRITICAL: You MUST update the project's .gitignore to exclude harness ephemeral files. This prevents uncommitted file clutter after /checkpoint.

Execute these steps:

Read the current .gitignore file (create if missing)
Check if .claude-harness/sessions/ pattern exists in the file

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

5d ago First seen · 90 lines · 43 tokens per session scan A e134f1b23f1e

Subscribe to this mod's changes

setup is a skill published in the GitHub repository panayiotism/claude-harness (79 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,107 once invoked, about $0.0002 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

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 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