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 skills add tomzx/agents --skill audit-maintainabilitygit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/audit-maintainability)<a href="https://agentmods.dev/skills/tomzx/agents/audit-maintainability"><img src="https://agentmods.dev/badge/skills/tomzx/agents/audit-maintainability/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.
<a href="https://agentmods.dev/skills/tomzx/agents/audit-maintainability"><img src="https://agentmods.dev/badge/skills/tomzx/agents/audit-maintainability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00138 | $0.02402 |
| Opus 5.5 | $0.00055 | $0.00961 |
| Sonnet 5.5 | $0.00028 | $0.00480 |
| Haiku 4.5 | $0.00014 | $0.00240 |
Grade A, and why
audit-maintainability 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 22d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TODAY=!date +%Y-%m-%d
Maintainability Audit (ISO/IEC 25010)
Audits the codebase for maintainability: how easily it can be modified to fix bugs, improve performance, or adapt to a changed environment.
It computes the architectural maintainability metrics that per-function scanners miss, then combines the find-* family's output into one maintainability scorecard.
This is the Maintainability characteristic of the ISO/IEC 25010 quality model.
What This Skill Adds Beyond the find-* Family
The find-* skills are per-function or per-file scanners (complexity, coverage, dead code, duplication, types).
They cannot see structure: which module depends on which, whether layers are respected, whether cycles exist, whether one module is a God object.
This skill computes those structural metrics and combines everything into one view.
| Source | What it provides here |
|---|---|
find-complexity-hotspots |
Modifiability: high cyclomatic complexity |
find-coverage-gaps |
Testability: untested code |
find-dead-code |
Reusability/analyzability: code that should be removed |
find-code-duplication |
Reusability: copy-paste to consolidate |
find-type-gaps |
Analyzability/modifiability: missing types |
| This skill (unique) | Modularity: coupling (fan-out), cohesion, circular dependencies, layering violations, God modules |
Prerequisites
- Working directory is the root of the repository
- Read
.sdlc/context/architecture.mdif present (declares intended layering rules this audit checks against) find-*skills available (invoked as read-only scanners)
What This Checks
| Sub-characteristic | Metric | How computed |
|---|---|---|
| Modularity | coupling / fan-out | count of distinct modules each module imports |
| Modularity | circular dependencies | import graph cycle detection |
| Modularity | layering violations | actual imports vs declared layers in architecture.md |
| Modularity | God modules | modules with LOC or import-count far above the median |
| Cohesion | mixed-concern modules | modules whose public functions span unrelated responsibilities (heuristic: divergent import sets) |
| Reusability | duplication | delegates to find-code-duplication |
| Analyzability | missing docs/types | delegates to find-documentation-gaps, find-type-gaps |
| Modifiability | complexity | delegates to find-complexity-hotspots |
| Testability | coverage gaps | delegates to find-coverage-gaps |
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.
- 22d ago Changed · +16 lines 08ce2140f2e9
- 23d ago Changed · +4 lines 35cb5a16c57a
- 24d ago Changed 68d44bff0039
- 2mo ago First seen · 212 lines · 138 tokens per session scan A 90cf8da429cc
audit-maintainability is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 138 tokens to every session and 2,402 once invoked, about $0.0006 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.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…