audit-harness

audit-harness is a skill for Claude Code, Codex from alchemiststudiosDOTai/tunacode. It costs 69 tokens per session (746 once invoked), scanned A, original, MIT.

A guide for checking the harness files and automated checks of tunacode-cli. These checks include commit hooks, push hooks, architecture rules, and continuous-integration workflows.

In plain words
What is it for?
Use it to audit HARNESS.md, verify hooks and CI workflows, check architecture gates, and explain what actually enforces the project's rules.
Why use it?
It treats skipped, mismatched, or failing checks as important findings and verifies each required check directly, so a summary or wrapper command cannot hide a problem.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions AGENTS.md.

Good fit Use it to audit HARNESS.md, verify hooks and CI workflows, check architecture gates, and explain what actually enforces the project's rules.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/alchemiststudiosdotai/tunacode/audit-harness
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.

Any agent
npx skills add alchemiststudiosDOTai/tunacode --skill audit-harness
Clone the repo
git clone --depth 1 https://github.com/alchemiststudiosDOTai/tunacode

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for audit-harness

README.md
[![agentmods](https://agentmods.dev/badge/skills/alchemiststudiosdotai/tunacode/audit-harness/github.svg)](https://agentmods.dev/skills/alchemiststudiosdotai/tunacode/audit-harness)
Your own site
<a href="https://agentmods.dev/skills/alchemiststudiosdotai/tunacode/audit-harness"><img src="https://agentmods.dev/badge/skills/alchemiststudiosdotai/tunacode/audit-harness/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.

agentmods 80×15 button for audit-harness

Your own site · 80×15
<a href="https://agentmods.dev/skills/alchemiststudiosdotai/tunacode/audit-harness"><img src="https://agentmods.dev/badge/skills/alchemiststudiosdotai/tunacode/audit-harness.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 69 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 746 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00069 $0.00746
Opus 5.5 $0.00028 $0.00298
Sonnet 5.5 $0.00014 $0.00149
Haiku 4.5 $0.00007 $0.00075

Measured 1mo ago against content hash be146927dfad, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

audit-harness 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 1mo 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.

docs/skills/audit-harness/SKILL.md · 102 lines

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.

Audit Harness

HARNESS.md is mission-critical. Audit it with zero tolerance.

Trigger

Use this skill when the user asks to:

  • audit HARNESS.md
  • verify harness accuracy
  • run pre-commit or pre-push hooks manually
  • confirm architecture or CI gates
  • explain what actually enforces the harness

Hard Rules

  • Treat any mismatch, omission, skipped gate, auto-fix, or failing check as a critical failure.
  • Never describe results as "mostly passing", "just one failure", or equivalent minimization.
  • State the exact failure first.
  • Explain the finding before changing code or docs.
  • Do not proceed with a fix until the user tells you to proceed.
  • During harness audits, never use make check, scripts/run_gates.py, or any loop/script wrapper as the primary audit path.
  • Run checks manually, one by one, in the same order they appear in the source-of-truth config.
  • If a hook modifies files, report the exact files immediately.
  • Do not revert hook changes unless the user explicitly asks.

Source Of Truth Order

Read these first:

  1. HARNESS.md
  2. .pre-commit-config.yaml
  3. Makefile
  4. tests/test_dependency_layers.py
  5. scripts/grimp_layers_report.py
  6. .github/workflows/*.yml
  7. docs/git/practices.md
  8. AGENTS.md

Manual Audit Procedure

Pre-commit

  1. Enumerate the active pre-commit hooks from .pre-commit-config.yaml.
  2. Start at the top.
  3. Run each hook manually:
uv run pre-commit run <hook-id> --all-files
  1. After each hook: state Passed, Failed, Skipped, or Modified files.
  2. If a hook fails, stop and explain why before proposing a fix.

Pre-push

  1. Enumerate the active pre-push hooks from .pre-commit-config.yaml.
  2. Run each one manually, one by one:
uv run pre-commit run <hook-id> --hook-stage pre-push --all-files
  1. Treat any failure as critical.

Architecture

  • tests/test_dependency_layers.py is the source of truth for grimp enforcement.
  • scripts/grimp_layers_report.py is report generation only.
  • scripts/run_gates.py is supplemental only and not canonical.

Read the full file on GitHub · 102 lines

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. 1mo ago First seen · 102 lines · 69 tokens per session scan A be146927dfad

Subscribe to this mod's changes

audit-harness is a skill published in the GitHub repository alchemiststudiosDOTai/tunacode (125 stars, last pushed 15d ago), licensed MIT. It adds 69 tokens to every session and 746 once invoked, about $0.0003 per session on Opus 5.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.