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/sairam0424/MindForgenpx agentmods add commands/sairam0424/mindforge/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/sairam0424/mindforge/harness-audit)<a href="https://agentmods.dev/commands/sairam0424/mindforge/harness-audit"><img src="https://agentmods.dev/badge/commands/sairam0424/mindforge/harness-audit.svg" alt="Measured on agentmods" 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.00031 | $0.00570 |
| Opus 5 | $0.00015 | $0.00285 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
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.
How it starts
The opening of the file, as written. The whole thing — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MindForge — Harness Audit Command
Usage: /mindforge:harness-audit [scope] [--format text|json]
Scopes: repo (default) | hooks | skills | commands | agents | security
Two-layer harness health check. The DETERMINISTIC layer is bin/harness-audit.js
(explicit file/config checks, reproducible, CI-gateable). The optional LLM layer
adds soft signals the deterministic checks cannot see (quality, drift, coherence).
Step 1 — Run the deterministic scorecard
node bin/harness-audit.js # text scorecard, repo scope
node bin/harness-audit.js --format json # machine-readable (for CI / dashboards)
node bin/harness-audit.js --scope security
The JSON contract is stable: overall_score, max_score, categories,
applicable_categories, rubric_version, checks[], top_actions[]. Categories:
Tool Coverage, Context Efficiency, Quality Gates, Memory & Learning, Eval Coverage,
Security Guardrails, Cost Efficiency, Governance & Identity.
Step 2 — (Optional) LLM soft-signal layer
For each category scoring below 10/10, inspect the failing checks in top_actions
and assess severity in context. The deterministic layer says what is missing; the
LLM layer judges whether it matters here and proposes the highest-leverage fix.
Step 3 — Report + AUDIT entry
Summarize the scorecard, then write a hash-chained AUDIT.jsonl entry:
{
"event": "harness_audit_completed",
"scope": "repo",
"overall_score": 0,
"max_score": 0,
"rubric_version": "2026-06-10",
"failing_categories": [],
"top_actions": []
}
Relationship to /mindforge:health
/mindforge:health calls this command as its deterministic layer. A regression
(e.g. the permissions.deny baseline removed, the Gemini settings mirror desynced,
the threat-model doc deleted) drops the Security Guardrails score and surfaces in
top_actions — making harness drift visible and CI-blockable.
Related: cross-harness compliance
npm run harness:compliance (bin/installer/harness-adapter-compliance.js --check)
validates the per-harness support matrix and gates documentation drift — distinct
from this scorecard, which audits the repo's own harness health.
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 · 60 lines · 31 tokens per session scan A 1fc4239143ac
harness-audit is a command published in the GitHub repository sairam0424/MindForge (0 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 570 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
p0-regulatory
Identifies regulatory requirements, DSGVO (GDPR) obligations, and legal knock-out criteria early on, before significant time is invested in the idea. A regulatory showstopper should be recognised as early as possible.
p3-infra-teststrategy
Defines test levels, test tools, coverage targets and critical test paths.
p3-infra-monitoring
Defines logging, metrics, alerting and error tracking.
p6-a11y
Systematically checks the application for accessibility. Each A11y dimension is a separate sub-skill.
sdd
Spec-driven dev loop. Plan once, then dev↔test↔eval loop until PRP spec satisfied. Local only, no PR.