loop-audit

A process check for projects that use a documented development loop, meaning a repeated cycle of planning, building, checking, and improving. It reviews the loop’s principles and decision gates, which are checkpoints for deciding whether work can proceed.

In plain words
What is it for?
Use it to audit a loop-enabled project, its loop files, and recent Git history. It produces a scored report in audit.md and suggests the next process improvement.
Why use it?
It shows whether the team followed its agreed working method, rather than checking only whether the product works. It also identifies gaps without changing the project itself.

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/hhamja/claude-code-harness/loop-audit
Any agent
npx skills add hhamja/claude-code-harness --skill loop-audit
Clone the repo
git clone --depth 1 https://github.com/hhamja/claude-code-harness

Made for: Claude Code, Codex.

Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 318 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 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.00025 $0.00318
Opus 5 $0.00013 $0.00159
Sonnet 5 $0.00005 $0.00064
Haiku 4.5 $0.00003 $0.00032

Measured yesterday against content hash 1432520346ad, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

loop-audit 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 yesterday.

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.

skills/loop-audit/SKILL.md · 19 lines

What it actually says

loop-audit — principle & gate adherence check

On-demand process audit, complementary to loop-run --verify-only (which grades the product against rubric.md). This grades whether the loop upheld its own method.

If .claude/loop/ does not exist: say so and point to /loopy:loop-init. Otherwise:

  1. Spawn the auditor agent with the instruction "audit this loop's process and decision-gate adherence". It reads .claude/loop/ and recent git history and returns one ## Auditor report (per-principle PASS/FAIL/UNKNOWN + verdict) plus a ## Gaps / next list. It modifies nothing.
  2. Print the report verbatim.
  3. Apply it (main agent does the write, mirroring how verifier reports are applied): OVERWRITE .claude/loop/audit.md with the report and a one-line timestamp header. audit.md is a human-facing artifact — committed like review.md, not gitignored.
  4. Suggest the next step: address the top gap, or resume with /loopy:loop-run.

Do not fix anything here yourself beyond writing audit.md; the gaps are for the next loop-run cycle or a human to act on. Safe to run anytime, including as the first command of a fresh session.

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. yesterday First seen · 19 lines · 25 tokens per session scan A 1432520346ad

Subscribe to this mod's changes

loop-audit is a skill published in the GitHub repository hhamja/claude-code-harness (1 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 318 once invoked, about $0.0001 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.

Related

Other skills, from other repositories