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/zhmxiaowo/opencode-simple/harness-auditgit clone --depth 1 https://github.com/zhmxiaowo/opencode-simpleWhat 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.00015 | $0.00407 |
| Opus 5 | $0.00008 | $0.00204 |
| Sonnet 5 | $0.00003 | $0.00081 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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 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.
This is a copy
86% identical to harness-audit — 5 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.
What it actually says
Harness Audit Command
Audit the current repository's agent harness setup 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)
What to Evaluate
Score each category from 0 to 10:
- Tool Coverage
- Context Efficiency
- Quality Gates
- Memory Persistence
- Eval Coverage
- Security Guardrails
- Cost Efficiency
Output Contract
Return:
overall_scoreout of 70- Category scores and concrete findings
- Top 3 actions with exact file paths
- Suggested ECC skills to apply next
Checklist
- Inspect
hooks/hooks.json,scripts/hooks/, and hook tests. - Inspect
skills/, command coverage, and agent coverage. - Verify cross-harness parity for
.cursor/,.opencode/,.codex/. - Flag broken or stale references.
Example Result
Harness Audit (repo): 52/70
- Quality Gates: 9/10
- Eval Coverage: 6/10
- Cost Efficiency: 4/10
Top 3 Actions:
1) Add cost tracking hook in scripts/hooks/cost-tracker.js
2) Add pass@k docs and templates in skills/eval-harness/SKILL.md
3) Add command parity for /harness-audit in .opencode/commands/
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.
- yesterday First seen · 64 lines · 15 tokens per session scan A ceaf6b9f5023
harness-audit is a command published in the GitHub repository zhmxiaowo/opencode-simple (2 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 407 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to harness-audit, differing in 5 lines, and is treated as a copy.
Other commands, from other repositories
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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.