harness-export

A skill for exporting the coding-agent tools installed across supported environments into a shareable harness.yaml configuration file.

In plain words
What is it for?
Saving and sharing a Harness Protocol v1 configuration; importing or restoring configurations is handled by a separate tool.
Why use it?
It gives teammates a record of the current setup that can be shared or committed to dotfiles, without manually listing each installed skill.

Skill for Claude CodeCodex

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/harnessprotocol/harness-kit/harness-export
Any agent
npx skills add harnessprotocol/harness-kit --skill harness-export
Clone the repo
git clone --depth 1 https://github.com/harnessprotocol/harness-kit

Made for: Claude Code, Codex.

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,024 The whole file, excluding the scripts and references it only reads on demand.
Security scan F 5 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.

ModelPer sessionOnce invoked
Fable 5 $0.00067 $0.03024
Opus 5 $0.00034 $0.01512
Sonnet 5 $0.00013 $0.00605
Haiku 4.5 $0.00007 $0.00302

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

Security

Grade F, and why

harness-export scanned grade F with 5 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 2d 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

> curl -fsSL https://raw.githubusercontent.com/harnessprotocol/harness-kit/main/harness-restore.sh | bash -s -- harness.yaml

Reads agent configuration directoriesmediumAgent snooping

.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.

cat .gemini/settings.json 2>/dev/null

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

cat .mcp.json 2>/dev/null

Enumerates other installed skillsmediumAgent snooping

Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.

ls ~/.claude/skills/ 2>/dev/null

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

> curl -fsSL https://raw.githubusercontent.com/harnessprotocol/harness-kit/main/harness-restore.sh | bash -s -- harness.yaml
plugins/harness-share/skills/harness-export/SKILL.md · 268 lines

How it starts

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

Export Your Harness Configuration

You are helping the user capture their current harness-kit setup into a harness.yaml file they can share with teammates or commit to their dotfiles repo.

This file follows the Harness Protocol v1 format — the open spec at harnessprotocol.ai. It is backward-compatible with harness-import (which handles both old and new formats).

Workflow Order (MANDATORY)

Follow these steps in order. Do not skip any step.


Step 1: Detect installed skills

Scan every skill directory across all 8 supported targets. Each subdirectory inside these directories is an installed skill:

  • ~/.claude/skills/ — Claude Code global skills
  • .cursor/skills/ — Cursor project-local skills
  • .github/skills/ — Copilot project-local skills
  • .agents/skills/ — Codex, and the agentskills.io standard shared location
  • .opencode/skills/ — OpenCode project-local skills
  • .windsurf/skills/ — Windsurf project-local skills
  • .gemini/skills/ — Gemini CLI project-local skills
  • .junie/skills/ — Junie project-local skills
ls ~/.claude/skills/ 2>/dev/null
ls .cursor/skills/ 2>/dev/null
ls .github/skills/ 2>/dev/null
ls .agents/skills/ 2>/dev/null
ls .opencode/skills/ 2>/dev/null
ls .windsurf/skills/ 2>/dev/null
ls .gemini/skills/ 2>/dev/null
ls .junie/skills/ 2>/dev/null

Collect the directory names from each location. Deduplicate by skill name across locations — if the same skill name appears in multiple directories, count it once. Track which platforms each skill was found in.

Show the user the combined result:

Found skills across AI tools:

  Claude Code (~/.claude/skills/):  research, explain, orient
  Cursor (.cursor/skills/):         research, explain
  Copilot (.github/skills/):        research
  Codex (.agents/skills/):          (none)
  OpenCode (.opencode/skills/):     (none)
  Windsurf (.windsurf/skills/):     research
  Gemini CLI (.gemini/skills/):     (none)
  Junie (.junie/skills/):           (none)

  Unique skills: research, explain, orient

Read the full file on GitHub · 268 lines

Files

What ships with it

1 file 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.

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. 2d ago First seen · 268 lines · 67 tokens per session scan F 894590c3c37c

Subscribe to this mod's changes

harness-export is a skill published in the GitHub repository harnessprotocol/harness-kit (10 stars, last pushed 3d ago), licensed Apache-2.0. It adds 67 tokens to every session and 3,024 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it F with 5 findings (downloads and executes remote code, reads agent configuration directories, reads mcp configuration). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

studio

Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.

AlpacaLabsLLC/skills-for-architects · 65 tokens

epd-to-spec

Write CSI specification language for EPD submittals and sourced GWP limits. Use to add embodied-carbon or EPD requirements to specs; not to parse, find, or compare EPDs.

AlpacaLabsLLC/skills-for-architects · 45 tokens

occupancy-calculator

Calculate code occupant loads by area with gross/net factors and jurisdiction checks. Use for "how many people can this space hold," IBC Table 1004.5, egress inputs, or occupancy-load reports; not for workplace headcount planning.

AlpacaLabsLLC/skills-for-architects · 55 tokens

zoning-analysis-nyc

Analyze NYC lot zoning, FAR, height, setbacks, uses, and buildable envelope from PLUTO and the Zoning Resolution. Use for "what can I build"; use nyc-bsa for relief and zoning-envelope for 3D visualization.

AlpacaLabsLLC/skills-for-architects · 57 tokens

workplace-programmer

Build office space programs through guided workplace strategy: area splits, room schedules, and planned seat counts. Use to program or size a workplace; not for code occupant-load calculations.

AlpacaLabsLLC/skills-for-architects · 40 tokens

workplan

Create a durable, execution-ready work plan for repository changes, operations, research, or AEC project delivery. Use when the user asks to plan, scope, sequence, coordinate, or break down multi-step work before acting. Do not use for floor plans, site plans, space planning, zoning calculations, building-code…

AlpacaLabsLLC/skills-for-architects · 72 tokens