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-loopnpx skills add joymin5655/Agent --skill harness-loopgit 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-loop)<a href="https://agentmods.dev/skills/joymin5655/agent/harness-loop"><img src="https://agentmods.dev/badge/skills/joymin5655/agent/harness-loop.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.00096 | $0.01376 |
| Opus 5 | $0.00048 | $0.00688 |
| Sonnet 5 | $0.00019 | $0.00275 |
| Haiku 4.5 | $0.00010 | $0.00138 |
Grade A, and why
harness-loop 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 4d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/harness-loop
HUMAN-ONLY-EDITED. This file is the §5 "program.md analog" (
docs/harness-improvement-plan.md§5.1): it states the loop's own rules. The loop agent reads it every iteration but must never editskills/harness-loop/SKILL.mditself — TARGET below is fixed to the reviewer-prompt pair precisely so a candidate cannot rewrite the regulation it runs under. Changing this file is a deliberate, human-reviewed act outside any loop session.
Mission
Apply the autonomous-improvement-loop procedure (§5,
docs/harness-improvement-plan.md) to this harness's own reviewer prompts.
Default TARGET (the only files a loop iteration may edit): agents/code-reviewer.md
and agents/security-reviewer.md. A hook-surface mission (editing
core/hooks/) is allowed only when the target hook already has its own
per-hook test battery (P1-3) — otherwise the grader's signal doesn't cover it
and the loop would be scoring blind.
This skill specializes /loop (skills/loop/SKILL.md) to one fixed
mission; all mechanical enforcement is still core/infra/loop-run.sh —
nothing here duplicates it.
Procedure
Work on branch harness-loop/<tag> (e.g. harness-loop/reviewer-precision-2026-08).
Steps 2–9 repeat per attempt, subject to the cap, timeout, and
circuit-breaker checked in step 9.
-
Check git state. Confirm the current branch and commit (
git status,git log -1) before touching anything — the loop must know exactly what "the mission's starting ref" (--base) means for this run. -
Edit TARGET only. Pick one improvement idea and change only the declared TARGET files — by default
agents/code-reviewer.mdandagents/security-reviewer.md. No other file changes in this step, tracked or untracked. -
Commit.
git committhe TARGET-only change. This commit is the candidateloop-run.sh attemptwill grade. -
Grade. Run:
bash core/infra/loop-run.sh attempt <slug> --desc "<idea, <=80 chars>"Internally this calls
bash core/tests/grade.sh --base <base ref> --target 'agents/(code-reviewer|security-reviewer)\.md'with output redirected to a run log — never straight into this conversation, which would be context pollution (C1 in the security review).--baseand--targetare mandatory: an unscoped grading call skips the TARGET-boundary check entirely, andgrade.shfails closed toharness_score: 0rather than score blind.
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.
- 4d ago First seen · 102 lines · 96 tokens per session scan A c05c24bfb7a2
harness-loop is a skill published in the GitHub repository joymin5655/Agent (2 stars, last pushed 10d ago), licensed MIT. It adds 96 tokens to every session and 1,376 once invoked, about $0.0005 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…
technocore-chat
Coordinate with other AI agents over plain HTTP GETs — shared rooms, durable notes, long-polling. No POST, no sockets, no client libraries, no account; a fetch tool is enough, and an MCP server fronts the same surface. Use when you need to leave a message for another agent, wait for one, or persist state across your…
goal-flight
Portable Goal Flight workflow for long-running repo work: planning, dispatch, review, recovery, file-backed resume.
shell-scripting
Use this skill when writing bash or zsh scripts, parsing arguments, handling errors, or automating CLI workflows. Triggers on bash scripting, shell scripts, argument parsing, process substitution, here documents, signal trapping, exit codes, and any task requiring portable shell script development.