Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/loulanyue/awesome-claude-notesnpx agentmods add commands/loulanyue/awesome-claude-notes/harness-auditWrote 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/commands/loulanyue/awesome-claude-notes/harness-audit)<a href="https://agentmods.dev/commands/loulanyue/awesome-claude-notes/harness-audit"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/harness-audit/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/commands/loulanyue/awesome-claude-notes/harness-audit"><img src="https://agentmods.dev/badge/commands/loulanyue/awesome-claude-notes/harness-audit.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.00000 | $0.00526 |
| Opus 5 | $0.00000 | $0.00263 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00053 |
Grade A, and why
harness-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 12d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- harness-audit — 100% identical, 0 lines differ
- harness-audit — 100% identical, 0 lines differ
- harness-audit — 100% identical, 0 lines differ
- harness-audit — 100% identical, 0 lines differ
- ccc-harness-audit — 94% identical, 4 lines differ
- harness-audit — 91% identical, 20 lines differ
- harness-audit — 83% identical, 14 lines differ
- harness-audit — 81% identical, 12 lines differ
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Harness Audit Command
Run a deterministic repository harness audit and return a prioritized scorecard.
Usage
/harness-audit [scope] [--format text|json]
scope(optional):repo(default),hooks,skills,commands,agents--format: output style (textdefault,jsonfor automation)
Deterministic Engine
Always run:
node scripts/harness-audit.js <scope> --format <text|json>
This script is the source of truth for scoring and checks. Do not invent additional dimensions or ad-hoc points.
Rubric version: 2026-03-16.
The script computes 7 fixed categories (0-10 normalized each):
- Tool Coverage
- Context Efficiency
- Quality Gates
- Memory Persistence
- Eval Coverage
- Security Guardrails
- Cost Efficiency
Scores are derived from explicit file/rule checks and are reproducible for the same commit.
Output Contract
Return:
overall_scoreout ofmax_score(70 forrepo; smaller for scoped audits)- Category scores and concrete findings
- Failed checks with exact file paths
- Top 3 actions from the deterministic output (
top_actions) - Suggested ECC skills to apply next
Checklist
- Use script output directly; do not rescore manually.
- If
--format jsonis requested, return the script JSON unchanged. - If text is requested, summarize failing checks and top actions.
- Include exact file paths from
checks[]andtop_actions[].
Example Result
Harness Audit (repo): 66/70
- Tool Coverage: 10/10 (10/10 pts)
- Context Efficiency: 9/10 (9/10 pts)
- Quality Gates: 10/10 (10/10 pts)
Top 3 Actions:
1) [Security Guardrails] Add prompt/tool preflight security guards in hooks/hooks.json. (hooks/hooks.json)
2) [Tool Coverage] Sync commands/harness-audit.md and .opencode/commands/harness-audit.md. (.opencode/commands/harness-audit.md)
3) [Eval Coverage] Increase automated test coverage across scripts/hooks/lib. (tests/)
Arguments
$ARGUMENTS:
repo|hooks|skills|commands|agents(optional scope)--format text|json(optional output format)
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.
- 12d ago First seen · 72 lines · 0 tokens per session scan A 62ea46a413be
harness-audit is a command published in the GitHub repository loulanyue/awesome-claude-notes (270 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 526 tokens. 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.
Other commands, from other repositories
bootstrap
Verifies and repairs the Claude Code Toolkit installation.
performance-audit
Find performance bottlenecks across the stack — queries, rendering, bundle size, memory.
debug
Systematic debugging — reproduce, isolate, fix, verify, and add regression test.
health-check
Run diagnostics on Claude Code toolkit configuration and status.
bug-plan-creator
Deep bug investigation with architectural fix plan generation - works with any executor (loop or swarm).
cg-indie-observability
Set up production observability for indie-scale apps — structured logging, uptime monitoring, error tracking, and basic metrics. Use when the user mentions logging, monitoring, alerts, error tracking, uptime checks, "how do I know if my app is down", Sentry, journalctl, structured logs, or wants to know what's…