Borrowing it
Nothing to install: this file belongs to chenklein26-maker/Harness-Starter. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chenklein26-maker/Harness-Starter/main/.claude/skills/harness-mode/SKILL.mdgit clone --depth 1 https://github.com/chenklein26-maker/Harness-StarterWrote 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/chenklein26-maker/harness-starter/harness-mode)<a href="https://agentmods.dev/skills/chenklein26-maker/harness-starter/harness-mode"><img src="https://agentmods.dev/badge/skills/chenklein26-maker/harness-starter/harness-mode/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/chenklein26-maker/harness-starter/harness-mode"><img src="https://agentmods.dev/badge/skills/chenklein26-maker/harness-starter/harness-mode.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 17 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00039 | $0.00466 |
| Opus 5 | $0.00019 | $0.00233 |
| Sonnet 5 | $0.00008 | $0.00093 |
| Haiku 4.5 | $0.00004 | $0.00047 |
Grade A, and why
harness-mode 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 9d 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.
What it actually says
Harness Mode
管理 .claude/.harness-state，控制 Harness 的行为策略。
支持的命令
切换模式
/harness-mode full → 完整检查，所有规则生效
/harness-mode hotfix → 紧急修复，跳过行数/文件数检查
/harness-mode tweak → 微调模式，仅 .env 保护
切换阶段
/harness-phase design → 设计阶段，宽松审查
/harness-phase build → 构建阶段，正常审查
/harness-phase fix → 修复阶段，收紧变更范围检查
查看当前状态
/harness-status → 显示当前阶段和模式
执行逻辑
当用户输入上述命令时：
- 读取
.claude/.harness-state（不存在则创建默认值{"phase":"build","mode":"full"}） - 修改对应的
mode或phase字段 - 更新
since为当前时间 - 写入文件
- 回显新状态
模式联动：
- 切换到
hotfix模式时，自动将 phase 设为fix - 切换到
tweak模式时，自动将 phase 设为design
示例
用户：/harness-mode hotfix
→ 写入 {"phase":"fix","mode":"hotfix","since":"2026-06-01T12:00:00Z"}
→ 回复：「已切换到热修复模式：阶段=fix, 模式=hotfix。将跳过行数/文件数检查。」
用户：/harness-status
→ 回复：「当前 Harness 状态：阶段=build, 模式=full (since 2026-06-01T10:00:00Z)」
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.
- 9d ago First seen · 56 lines · 39 tokens per session scan A 93b81d0bde8b
harness-mode is a skill published in the GitHub repository chenklein26-maker/Harness-Starter (119 stars, last pushed 2mo ago), licensed MIT. It adds 39 tokens to every session and 466 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.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.