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-issue-debug)<a href="https://agentmods.dev/skills/oeftimie/vv-claude-harness/harness-issue-debug"><img src="https://agentmods.dev/badge/skills/oeftimie/vv-claude-harness/harness-issue-debug/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-issue-debug"><img src="https://agentmods.dev/badge/skills/oeftimie/vv-claude-harness/harness-issue-debug.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.00103 | $0.02292 |
| Opus 5 | $0.00051 | $0.01146 |
| Sonnet 5 | $0.00021 | $0.00458 |
| Haiku 4.5 | $0.00010 | $0.00229 |
Grade B, and why
harness-issue-debug scanned grade B 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 10d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
f"fix with: chmod 600 {key_file}", How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Debug
Opens a live, interactive repair session on a piece of work that stopped: a harness
feature marked failed, or a Linear issue the external runner parked after exhausting
its self-heal attempts. This skill is the hands-on counterpart to harness-issue-prep: where
harness-issue-prep fixes a spec before implementation starts, harness-issue-debug fixes an
implementation (or the spec behind it) after something already went wrong.
Mode is selected by the shape of the argument:
F0NN(matches a feature id in.harness/features.json): local mode.- An issue key matching
^[A-Z]+-[0-9]+$(for exampleENG-123): runner mode.
If the argument matches neither shape, ask which mode the user means before proceeding.
Local Mode (F0NN)
Step 1: Load context. Read the feature from .harness/features.json and surface, in
one block, everything a debugging session needs before touching code:
Feature F0NN: [description]
Status: failed
Failure reason: [failure_reason]
Notes: [notes]
Correction cycles: [correction_cycles]
Scope: [scope]
Step 2: Check out the branch. If notes names a branch, check it out. If it does not,
ask the user which branch to use before continuing; do not guess.
Step 3: Establish the baseline. Run ./.harness/init.sh to confirm the checked-out
branch builds and to see the current failure state directly, not secondhand through
failure_reason.
Step 4: Iterate the fix. This is a normal interactive session: write a failing test, implement, confirm green, refactor, repeat. No special ceremony beyond the harness's usual TDD discipline applies here; the only thing that distinguishes this session from any other feature work is that it starts from a known failure instead of a blank feature.
Step 5: Exit route. Exactly one of three, decided with the human present:
- Fixed and the human is satisfied. Set
statusto"pending", not"passing"; the quality gate (verify-task-quality.shonTaskCompleted) is what earns"passing", and this skill does not shortcut it. Clearfailure_reason. - The spec was the real problem, not the code. Run
harness-issue-prep F0NNto fix the description before any further implementation attempt. - Abandoned this session. Keep
status: "failed". Updatefailure_reasonwith what was learned this round, even if the answer is still "unresolved": a stalefailure_reasonfrom a prior attempt is worse than an updated one that says what was ruled out.
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.
- 10d ago First seen · 182 lines · 103 tokens per session scan B be5916861133
harness-issue-debug is a skill published in the GitHub repository oeftimie/vv-claude-harness (19 stars, last pushed 17d ago), licensed MIT. It adds 103 tokens to every session and 2,292 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.