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 commands/tpavanipradeep/everything-claude-code/harness-auditgit clone --depth 1 https://github.com/tpavanipradeep/everything-claude-codeWhat 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.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 3d 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.
This is a copy
100% identical to harness-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 3d ago First seen · 72 lines · 0 tokens per session scan A 62ea46a413be
harness-audit is a command published in the GitHub repository tpavanipradeep/everything-claude-code (104 stars, last pushed 5mo 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. It is 100% identical to harness-audit, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.