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 skills/okuzpe/midas-harness/midas-precommitnpx skills add okuzpe/midas-harness --skill midas-precommitgit clone --depth 1 https://github.com/okuzpe/midas-harnessWrote 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/skills/okuzpe/midas-harness/midas-precommit)<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-precommit"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-precommit.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 | $0.00065 | $0.01484 |
| Opus 5 | $0.00032 | $0.00742 |
| Sonnet 5 | $0.00013 | $0.00297 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
midas-precommit 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
midas-precommit — engine quality bar (≥ 80)
Guard + state:
<paths.engine>/templates/skill-state-ritual.md(+AGENTS.md§ Safety / Path resolution). Engine-only. Rubric:docs/precommit-gate.md. Mechanical floor:node scripts/precommit-eval.mjs(staged skill linter + doctor).
Standing pre-commit gate for the midas-harness engine repo. Scores the same harness-fitness dimensions used in full audits. Overall must be ≥ 80 or the verdict is fail — do not commit.
Skill linter: scripts/skill-quality-check.mjs is the mechanical linter for harness/skills/ and harness/agents/ (not ESLint). Precommit runs it with --staged --strict-warns only — warnings on touched skills fail per harness/rules/skill-quality.md. Full-engine 0-warn scan stays in CI (npm test).
Does / Does not
| Does | Does not |
|---|---|
| Abort unless cwd is midas-harness engine | Run on product installs / template trees |
| Run mechanical floor + score 12 dimensions 1–100 | Advance stage or pass lifecycle gates |
Require overall ≥ 80 to verdict=pass |
Replace /midas-align, /midas-doctor, or CI |
Optional freeze under runs/precommits/ (contributors) |
Ship this skill to cli/template / harness/plugins/midas |
Engine guard (hard)
- Confirm engine:
package.json→"name": "midas-harness"andscripts/test.mjsexists. - Otherwise print: ABORT —
/midas-precommitis engine-only; use/midas-align→ STOP.
Procedure
0. Sandbox dry-run (proposed, not forced)
If the staged diff touches harness/skills/** or harness/rules/**, AskQuestion once: run
/midas-sandbox --smoke for the touched skill first, or skip. Recommended: --smoke (not
skip). This is not a mechanical gate — /midas-sandbox is engine-only, cost-gated
(composer-2.5, never -fast), and optional; see sandbox/README.md. Never block the commit on
the user's answer.
1. Mechanical floor
node scripts/precommit-eval.mjs --json
If exit ≠ 0 or mechanical_ok is false → verdict=fail, list hard_fails, STOP (fix before re-scoring).
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 · 125 lines · 65 tokens per session scan A 2ffefeac6cf2
midas-precommit is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 65 tokens to every session and 1,484 once invoked, about $0.0003 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-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…