What is midas-hygiene?

A cleanup workflow for product code and documentation in a repository. It looks for unused code paths, orphaned files, and inconsistencies between records and documents.

Use it to run product-tree cleanup scans, review large diffs, and produce an optional list of items that could be removed.

It helps identify repository clutter and documentation drift before a large change is closed or after adopting an existing codebase.

How okuzpe/midas-harness configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to okuzpe/midas-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/okuzpe/midas-harness/main/.agents/skills/midas-hygiene/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/okuzpe/midas-harness

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-hygiene/github.svg)](https://agentmods.dev/skills/okuzpe/midas-harness/midas-hygiene)

Your own site

<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-hygiene"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-hygiene/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/okuzpe/midas-harness/midas-hygiene"><img src="https://agentmods.dev/badge/skills/okuzpe/midas-harness/midas-hygiene.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,171 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00073	$0.01171
Opus 5.5	$0.00029	$0.00468
Sonnet 5.5	$0.00015	$0.00234
Haiku 4.5	$0.00007	$0.00117

Measured 1mo ago against content hash ef08fc909ec9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

midas-hygiene 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 1mo 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.

.agents/skills/midas-hygiene/SKILL.md · 82 lines

How it starts

The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.

midas-hygiene — product repo cleanup

Guard + state: <paths.engine>/templates/skill-state-ritual.md (+ AGENTS.md § Safety / Path resolution). Surface: primary — human-typed; parents (/close-sprint Step 0) path-pass this body (read + run — not Skill-tool). Scope: product code + {product}/* only. Never .harness/engine adapters, doctor, or align.

Standing repo hygiene (not a phase gate): find dead weight in the product tree, report, optionally fix with explicit confirm. Complements Layer C Sync (/midas-doctor, /midas-align) — those are install/adapter health, not product dead-flow.

Does / Does not

Does	Does not
Path-pass `midas-sweep` with scope `product` (or `code` / `docs`)	Run sweep scope `harness` or legacy `all` (includes harness)
Path-pass `midas-lean-review` when mode is `lean` or fat-diff `all`	Advance `stage` or pass Phase-8 alone
Reuse `{runs}/sweeps/sweep-NN.md` + optional `lean-NN.md`	Replace `/close-sprint`, tribunal, security, or doctor

Modes (AskQuestion or args)

Mode / arg	Path-pass
`all` (default)	sweep `product`; if working-tree diff is large/fat UI-feature, also lean-review (`--scope diff`)
`dead-flows` / `code`	sweep `code`
`docs`	sweep `docs`
`lean`	lean-review only (`--scope diff` default)
`report-only`	same as chosen mode without `--fix` / apply

--fix → forward to sweep --fix only after the report; lean apply only if the human asks after the delete-list.

Procedure

Read paths.state. Resolve mode from args or one AskQuestion (default all).
Sweep leg (unless mode=lean only): Read and follow <paths.engine>/skills/midas-sweep/SKILL.md with scope product (or code/docs per mode). Never pass harness or all. Expect harness_drift=0 in the tally for product scopes (R6).
Lean leg: When mode is lean, or mode is all and the diff is fat (many files / UI feature), path-pass <paths.engine>/skills/midas-lean-review/SKILL.md (optional --freeze).
Report combined summary; recommended next = /close-sprint when in an active sprint, else /midas-status.
Optional fix: only with explicit human OK (sweep --fix / lean apply). Prefer archive over hard delete.

Read the full file on GitHub · 82 lines

Changes

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.

1mo ago Changed ef08fc909ec9
2mo ago First seen · 82 lines · 73 tokens per session scan A b5ea3964eaa2

Subscribe to this mod's changes

midas-hygiene is a skill published in the GitHub repository okuzpe/midas-harness (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 1,171 once invoked, about $0.0003 per session on Opus 5.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.

Code review Debugging

sync-bridge

Reviews and guides Chromium Sync Model API (DataTypeSyncBridge) implementations, including DataTypeStore persistence and forwards/backwards compatibility for sync specifics. Use when implementing or reviewing a DataTypeSyncBridge subclass, DataTypeStore usage, sync metadata persistence, conflict resolution, or…

chromium/chromium · 109 tokens

sync-model-processor

Reviews changes to Chromium Sync model internals in components/sync/model/, including ClientTagBasedDataTypeProcessor, ClientTagBasedRemoteUpdateHandler, ProcessorEntity, ProcessorEntityMetadata, and ProcessorEntityTracker. Use when modifying or reviewing processor state transitions, entity metadata tracking, conflict…

chromium/chromium · 98 tokens

adversarial-reviewer

Stress-test a code change for concrete correctness defects, unsafe assumptions, and failure modes. Use when the user explicitly asks for an adversarial review, a deep bug hunt, or to tear a change apart, or to check your own change before submitting it. Do not use for ordinary review, style feedback, or general…

emdash-cms/emdash · 72 tokens

gsd-ns-review

Invoke this Pi skill with /skill:gsd-ns-review.

open-gsd/gsd-core · 16 tokens

gitnexus

A code-graph analysis add-on for examining an existing codebase, including symbols, call paths, execution flows, and effects across repositories. It can query GitNexus through its command-line or MCP interfaces.

hashgraph-online/awesome-codex-plugins · 58 tokens

issue

Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…

jeremylongshore/tons-of-skills-marketplace · 115 tokens

midas-harness: Skill for Claude Code