audit · git:20261103.2ca7d9a · 2026-11-03 · sha256 4e7f6668fc09522d
audit git:20261103.2ca7d9aA
Immutable. This exact content never changes and is served at /api/v1/blob/4e7f6668fc09522d.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2xtxpw27vzdln2pp/4e7f6668fc09522d0dfcbc93c2bd20dfc95274261f879638a706be9598be16ac.json
Then /plugin install audit@markdownregistry-2xtxpw27vzdln2pp in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: audit
description: |-
Audit this repository.
disable-model-invocation: true
metadata:
internal: true
---
# Domfiles Repository Audit
## Resolve Audit Scope
The table lists higher-precedence rules first. Apply publication audit scope when that mode is selected and default scope otherwise.
| Priority | Rule |
| --- | --- |
| Security exclusions | Preserve credential protection, access controls, and higher-priority read restrictions, including the [exclusion of `home/.config/fish/local.fish`](../../../AGENTS.md#scope). Explicit scope doesn’t bypass these boundaries. |
| Explicit scope | Override only the corresponding publication audit or default scope rules. Interpret the request through [Audit Path Selection](references/audit-path-selection.md). |
| Publication audit | Use this mode when an audit evaluates the tracked `HEAD` tree for public disclosure. Resolve the reportable scope from the tree’s regular files rather than the active checkout, and exclude every untracked or ignored path. Apply the [publication audit requirements](#inspect-publication-audit-trees). |
| Default scope | Start with Git-tracked regular files, exclude symbolic links and untracked or ignored paths, and apply every other default inclusion, exclusion, and exemption from applicable `AGENTS.md` files. |
1. Read every applicable `AGENTS.md` file before reviewing any other repository content.
2. Apply the precedence table above to resolve the reportable scope.
3. Inspect content outside the reportable scope only when needed as supporting evidence for a path in that scope. Security exclusions still apply, and supporting evidence doesn’t become reportable.
## Inspect Publication Audit Trees
By default, inspect tracked `HEAD` directly rather than materializing an isolated filesystem copy. Capture its exact commit once and use that commit for every read-only Git inspection. Select the repository root through the tool’s working directory parameter or `git -C <repository-root>`, and do not let a moving ref, the current shell subdirectory, or the working tree narrow or alter the evidence.
An explicit user direction may select another route, but it doesn’t establish that an existing tool preserves the selected tree. Don’t design or implement a materializer without authorization for that additional work. When the audit requires an isolated copy, follow [Publication Audit Staging](references/publication-audit-staging.md).
## Audit Contents
For every path in the reportable scope:
- Check for redundancies, inconsistencies, typos, and structural or type issues.
- Ensure there is no dead or unused code.
- Report code that reimplements behavior already available in the language, standard library, or existing shared utilities in this repository. When the audit has a comparison baseline, apply this check specifically to new code.
- Include comments and documentation in the analysis. Report factual claims in comments or documentation that no longer match current repository behavior, the supported environment, or applicable project rationale, or that no longer make sense in their current context.
- Report documentation that duplicates durable details or violates the [documented authority and ownership boundaries](../../../AGENTS.md#agent-documentation).
- Apply every relevant repository instruction and loaded domain skill policy. Use domain skills to supplement the audit with domain-specific checks and verification, rather than as separate audit workflows.
## Keep Audits Read-Only
- Don’t modify repository files or run linters or formatters as part of the analysis, including read-only check modes.
- Don’t report findings outside the reportable scope.
- Base findings on the current repository contents under review. When current behavior must be verified, use authoritative installed tool behavior or official documentation and source as supporting evidence.
- Never speculate about intent or hypothetical implementations.
## Report Audit Results
Before reporting a finding, check `.agents/PROJECT.md` for project rationale that explains or settles it.
Continue until the entire scope has been reviewed, then report all findings together.
Follow the global [communication](../../GLOBAL.md#communication) and [**Findings**](../../GLOBAL.md#findings) requirements, then:
1. Lead with the findings. If there are none, state that the audit found no reportable issues.
2. State the resolved reportable scope.