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.
npx agentmods add skills/shipwithai/shipwithai-plugins/harness-setupnpx skills add ShipWithAI/shipwithai-plugins --skill harness-setupgit clone --depth 1 https://github.com/ShipWithAI/shipwithai-pluginsWrote 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.
[](https://agentmods.dev/skills/shipwithai/shipwithai-plugins/harness-setup)<a href="https://agentmods.dev/skills/shipwithai/shipwithai-plugins/harness-setup"><img src="https://agentmods.dev/badge/skills/shipwithai/shipwithai-plugins/harness-setup.svg" alt="Measured on agentmods" height="20"></a>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.01200 |
| Opus 5 | $0.00022 | $0.00600 |
| Sonnet 5 | $0.00009 | $0.00240 |
| Haiku 4.5 | $0.00004 | $0.00120 |
Grade A, and why
harness-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.
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Setup
Analyze your project and generate a production-ready Claude Code harness. Works for any stack — reads your actual code instead of filling templates.
When to Use
- Project missing a CLAUDE.md, or existing one is generic/outdated
- Need settings.json with balanced permission rules
- Want validate-command.py + protect-files.py safety hooks
Step 0: Check for Existing CLAUDE.md
If CLAUDE.md exists and has content:
Ask: "Found existing CLAUDE.md. Overwrite with new harness, or skip?"
- Skip → stop
- Overwrite → continue
Step 1: Deep Project Scan (parallel reads)
Read references/analysis-guide.md for extraction instructions. Then run all reads simultaneously.
Read whichever of these exist:
- Root config files:
package.json,pom.xml,pyproject.toml,go.mod,Cargo.toml,composer.json,Gemfile,build.gradle Makefile(if exists).env.example(if exists)- Directory structure: glob
**to depth 2 - One representative source file (entry point or a typical service/controller)
- One test file (look in
tests/,test/,spec/,src/test/,__tests__/)
After reading, extract answers to:
| Question | Source |
|---|---|
| Stack | Config files + deps (see analysis-guide.md §Stack Identification) |
| Run/build/test/lint commands | scripts in package.json, Makefile targets, pom.xml goals |
| Directory structure | Glob result — top 3–5 meaningful dirs |
| ORM/database | Deps + schema file location |
| Env vars needed | .env.example or grep process.env./os.getenv( in source |
| Test framework + location | Test file imports + directory name |
| Package manager | Lockfile presence: bun.lockb→bun, pnpm-lock.yaml→pnpm, yarn.lock→yarn, else npm |
| Port | Dev script, application.properties:server.port, or stack default |
Show summary before asking questions:
🔍 Scan complete
Stack: Go (Gin framework)
Commands: run: go run ./cmd/... | test: go test ./... | lint: golangci-lint run
Structure: cmd/, internal/, pkg/, migrations/
Database: GORM — models in internal/models/
Tests: Go testing (testify) in *_test.go files
Port: 8080
Env vars: DATABASE_URL, JWT_SECRET, PORT
What ships with it
7 files 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.
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 · 139 lines · 43 tokens per session scan A d94fc0ed66ad
harness-setup is a skill published in the GitHub repository ShipWithAI/shipwithai-plugins (10 stars, last pushed 22d ago), licensed MIT. It adds 43 tokens to every session and 1,200 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-31.
Other skills, from other repositories
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
espalier-migrate
Migrate an existing harness/espalier install to the current Espalier version — auto-detects which of v0.1→v0.2, v0.3→v0.4, v0.4→v0.5, the v0.5.3 coder-agent patch, v0.5→v0.6 (Stage 1 grill), v0.6→v0.7 (read-only /espalier-ask lane), v0.7→v0.8 (requirements approval gate), the v0.8.1 impact-analysis agent patch, the…
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.