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/joymin5655/agent/harness-helpnpx skills add joymin5655/Agent --skill harness-helpgit clone --depth 1 https://github.com/joymin5655/AgentWrote 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/joymin5655/agent/harness-help)<a href="https://agentmods.dev/skills/joymin5655/agent/harness-help"><img src="https://agentmods.dev/badge/skills/joymin5655/agent/harness-help.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.00041 | $0.00833 |
| Opus 5 | $0.00020 | $0.00417 |
| Sonnet 5 | $0.00008 | $0.00167 |
| Haiku 4.5 | $0.00004 | $0.00083 |
Grade A, and why
harness-help 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/harness-help
You don't remember every skill, so ask. Most work travels one main flow;
everything else is standalone. Each skill below is documented in its own
skills/<name>/SKILL.md — this router only says when to reach for which.
The main flow: idea → shipped
/spec <slug>— turn a fuzzy request intospec.md+plan.mdunder.agent/plans/<slug>/, then route to plan approval (ExitPlanMode). Add--interviewwhen the request is fuzzy enough that a wrong guess would commit the spec to the wrong shape, or--score-candidateswhen the field of problems/approaches is wide enough that the pick should be scored, not asserted. Approval is what unlocks editing —spec-gatestops asking once the plan-approval flag exists./supervise <slug>— run the approved plan wave by wave, dispatching specialists per the delegation contract and auditing after each wave.--goal-modefor budgeted, resumable runs./verify-completion <claim>— before accepting any "done": a fresh context re-checks the claim mechanically, then a refute-by-default judge./supervisecalls this at its completion step; reach for it directly whenever a builder's word is the only evidence./wrap— commit + PR with the safety gates (gitleaks, risk areas) intact.--auto-push/--auto-mergeare opt-in escalations.
A single small edit needs none of this — just make the edit; the gates scope trivial work out by design.
Standalone
/harness-audit— read-only health check of the harness itself: oneverify-all.shdry-run, a per-check table, the doc-reality verdict named. Run it before a release or after a structural change./persona-review <target>— seat a panel of grounded Korean citizen personas in front of a piece of UX/copy/content and report how ordinary users would react. A user-perspective lens besidecode-reviewer(correctness) andsecurity-reviewer(vulnerabilities) — it judges experience, not code./worker-setup— install → auth → verify onboarding for the cross-vendor worker lanes (codex, antigravity, grok, kiro), with a cost-model briefing before anything installs. Reach for it whensetup.sh --doctorWARNs about a worker lane, or/council-reviewreports a lane absent./project-init(command) — scaffold a consumer project withCLAUDE.md, rules, andgitleaks.toml.
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 · 67 lines · 41 tokens per session scan A 2347575a0ff6
harness-help is a skill published in the GitHub repository joymin5655/Agent (2 stars, last pushed 2d ago), licensed MIT. It adds 41 tokens to every session and 833 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
regex-mastery
Use this skill when writing regular expressions, debugging pattern matching,optimizing regex performance, or implementing text validation. Triggers on regex, regular expressions, pattern matching, lookahead, lookbehind, named groups, capture groups, backreferences, and any task requiring text pattern matching.
background-watch-hook
Use vibe watch to run a managed Harness waiter that returns to the same conversation later. Best for reviews, CI, files, logs, and other wait-now-continue-later workflows.
pr-delivery-loop
The implementation-lane standard for delivering a PR across the Avibe repositories (avibe, avibe-backend, avibe-docs, avault, and vault-sandbox) — branch/scope rules, contracts, Codex-bot review-loop discipline, and close-out criteria. Use this skill for every implementation task in these repos, regardless of agent…
use-avibe-harness
Use Avibe Harness for durable Agent delegation, Sessions, scheduled Tasks, Watches, Runs, queues, and work that must continue beyond the current turn.
use-show-pages
Build, inspect, update, or share an Avibe Show Page when a visual explanation, diagram, dashboard, report, or interactive prototype would materially help.
use-avibe-vault
Use Avibe Vault for API keys, tokens, passwords, protected credentials, authenticated HTTP requests, or digest signing without exposing secret values to the agent.