harness-config-audit SKILL.md skillA
harness-config-audit from iamakbarsha1/whetstone is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add iamakbarsha1/whetstone/harness-config-audit@git:20261024.08b5719Pins git:20261024.08b5719 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- iamakbarsha1/whetstone
- Path
skills/harness-config-audit/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261024.08b5719, committed Oct 24, 2026
- First version recorded
- Oct 24, 2026
- Size
- 10,010 bytes
- Repository stars
- 4
- License
- CC-BY-4.0
Use when applying an external write-up — an article, a "here is my setup" post, a best-practice guide, a vendor doc — to a configuration you already run, and the ask is some form of "how do I apply this to mine". The deliverable is a per-surface delta, not a restatement of the guide: walk a FIXED list of configuration surfaces (always-loaded instructions, path-scoped rules, skills, subagents, permission allow/deny/ask rules, hooks by event, tool and MCP servers, model and effort settings…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Harness Config Audit **Type:** Open-source — client-agnostic methodology, no project-specific detail. **Created by akbarsha — https://github.com/iamakbarsha1** Distilled from an audit of a whole agent configuration against a third-party article, improvised because no fixed surface list existed — it found a real high-impact gap, and it also had to catch a model identifier the article named that did not exist in the running environment. **Licence:** Released under CC BY 4.0 — share and adapt for any purpose with credit. Full text: `LICENSE` at the repository root. **Feedback & Support:** If a rule here proves wrong or needs sharpening, open an issue on the repository or contact the author at the profile link above. If the problem is the agent not following a rule below rather than the rule itself, that's an execution failure — acknowledge and correct it. ## The core rule An external write-up describes someone else's finished configuration. Your reader already has one. The deliverable is the difference between the two — which layers are already covered, which are genuinely missing — and you cannot state a difference you have not enumerated. So the audit has a fixed shape: …
Read the whole file at its exact version.
How to install
mdr add iamakbarsha1/whetstone/harness-config-audit@sha256:d51b51cbd3108d18The line at the top of this page pins the label git:20261024.08b5719, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_xb4bmui7v7ksodvc)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Oct 24, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261024.08b5719 latest | 2026-10-24 | 08b5719 | 10,010 B | A | view · diff |
| git:20261024.d153cce | 2026-10-24 | d153cce | 9,822 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10010 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
iamakbarsha1/whetstone · 4 stars · license CC-BY-4.0 · pushed 2026-10-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_xb4bmui7v7ksodvc GET https://markdownregistry.com/api/v1/resolve?ref=iamakbarsha1/whetstone/harness-config-audit GET https://markdownregistry.com/api/v1/blob/d51b51cbd3108d18bbe1b96760156f8e8ef86872533de63dc793352b2e00d91d
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.