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.
/plugin marketplace add oeftimie/vv-claude-harness/plugin install vv-harnessWrote 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/oeftimie/vv-claude-harness/harness-init)<a href="https://agentmods.dev/skills/oeftimie/vv-claude-harness/harness-init"><img src="https://agentmods.dev/badge/skills/oeftimie/vv-claude-harness/harness-init/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.
<a href="https://agentmods.dev/skills/oeftimie/vv-claude-harness/harness-init"><img src="https://agentmods.dev/badge/skills/oeftimie/vv-claude-harness/harness-init.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00056 | $0.04627 |
| Opus 5 | $0.00028 | $0.02313 |
| Sonnet 5 | $0.00011 | $0.00925 |
| Haiku 4.5 | $0.00006 | $0.00463 |
Grade A, and why
harness-init scanned grade A with 1 finding 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 11d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
out = subprocess.check_output(["claude", "--version"], stderr=subprocess.DEVNULL, text=True) How it starts
The opening of the file, as written. The whole thing — 452 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Initializer
Follow these steps in order. Do not skip steps. Ask the user when indicated.
Step 1: Gather Requirements
Ask the user (if not already provided):
- What are you building? (brief description)
- What's the tech stack? (language, framework, build tool)
- Any existing code to preserve?
If the user provided this information in their initial message, proceed without asking.
Step 2: Capture Git Identity
git config user.name
git config user.email
ssh -T [email protected] 2>&1 || true
cat ~/.ssh/config 2>/dev/null | head -30
Record the active identity. Ask the user to confirm:
I detected:
- Git user: [name] <[email]>
- SSH identity: [key file or host alias]
Is this correct for this project? If you use multiple GitHub accounts, tell me which one this project belongs to.
Store the confirmed identity in .harness/harness.json.
Step 3: Create .harness/ Directory
Never hand-transcribe the framework-fixed files below into a project -- run
${CLAUDE_PLUGIN_ROOT}/scripts/stamp.sh, which emits every one of them deterministically
from an answers file. Adapted from Setlist's two-phase bootstrap doctrine (Alex Ciortan,
CC BY 4.0): "Never hand-write what a stamp can emit; never stamp what a decision shapes."
First, confirm the build hook. If the detected stack is one of typescript,
swift, python, go, or rust, show the user the exact PostToolUse hook the stamp
is about to wire in (the content of skills/harness-init/templates/posttooluse-<stack>.json
-- it catches type/build errors after edits without blocking the agent, since hooks run
async) and wait for confirmation before continuing. Any other stack: say plainly that no
PostToolUse hook is available for it, and proceed.
Write the answers file:
mkdir -p /tmp/vv-harness-stamp
cat > /tmp/vv-harness-stamp/answers.txt <<EOF
project_name=PROJECT_NAME
stack=DETECTED_OR_SPECIFIED_STACK
mode=new
EOF
mode=new is correct here; mode=upgrade exists in stamp.sh for re-stamping an
existing project and is not used by this skill.
What ships with it
14 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.
- commit-gate.sh.template 76 KB
- enforce-scope.sh.template 108 KB
- harness_state.py.template 10.0 KB
- init.sh.template 9.8 KB
- templates/features.json.tmpl 117 B
- templates/harness.json.tmpl 133 B
- templates/posttooluse-go.json 330 B
- templates/posttooluse-python.json 335 B
- templates/posttooluse-rust.json 327 B
- templates/posttooluse-swift.json 330 B
- templates/posttooluse-typescript.json 358 B
- templates/settings.json.tmpl 1.4 KB
- verify-git-identity.sh.template 8.1 KB
- verify-task-quality.sh.template 24 KB
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.
- 11d ago First seen · 452 lines · 56 tokens per session scan A ef2258d5a2a9
harness-init is a skill published in the GitHub repository oeftimie/vv-claude-harness (19 stars, last pushed 18d ago), licensed MIT. It adds 56 tokens to every session and 4,627 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.