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-sdlcgit 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-sdlc)<a href="https://agentmods.dev/skills/tomzx/agents/audit-sdlc"><img src="https://agentmods.dev/badge/skills/tomzx/agents/audit-sdlc/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-sdlc"><img src="https://agentmods.dev/badge/skills/tomzx/agents/audit-sdlc.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.00023 | $0.02496 |
| Opus 5.5 | $0.00009 | $0.00998 |
| Sonnet 5.5 | $0.00005 | $0.00499 |
| Haiku 4.5 | $0.00002 | $0.00250 |
Grade A, and why
audit-sdlc 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit SDLC
Runs multiple audit skills against the project and produces a unified findings report ranked by severity and impact. Optionally turns the highest-priority findings into issues.
Runs audit skills that scan code, dependencies, and infrastructure. Does not modify any files. Safe to run at any time.
The audit skills map to the ISO/IEC 25010 software quality model.
audit-sdlc is the coordinator for that model: it runs whichever per-characteristic skills exist and produces the unified quality report.
ISO/IEC 25010 Quality Model Mapping below lists which characteristics are covered today and which are planned gaps.
Prerequisites
- Apply the shared SDLC conventions in
skills/sdlc/references/shared.md. - Working directory is the root of the repository
.sdlc/directory exists (run/sync-sdlcfirst if not)- Read any files present under
.sdlc/context/for project-level context
Audit Skills by Category
Diagnose
Surface what is risky or actively unstable.
| Skill | What it finds |
|---|---|
audit-dependencies |
CVEs, outdated packages, unmaintained dependencies, license issues |
audit-security |
Hardcoded secrets, injection risks, missing auth, insecure patterns |
analyze-git-churn |
High-churn files indicating instability or code that needs refactoring |
Harden
Reduce structural risk before changing code.
| Skill | What it finds |
|---|---|
find-complexity-hotspots |
High cyclomatic complexity, excessive length, deep nesting |
find-type-gaps |
Missing type annotations |
find-coverage-gaps |
Missing or insufficient test coverage |
Clean
Remove what no longer belongs.
| Skill | What it finds |
|---|---|
find-dead-code |
Unused functions, classes, variables, exports, feature flags |
find-code-duplication |
Copy-pasted blocks and near-duplicate logic |
Observe
Monitor production health and surface runtime issues.
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 · +15 lines 2bc9ea17b886
- 23d ago Changed · -4 lines dd99c1a86495
- 24d ago Changed 6035c5792aaa
- 2mo ago First seen · 240 lines · 23 tokens per session scan A f9a62549e0c7
audit-sdlc is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 23 tokens to every session and 2,496 once invoked, about $0.0001 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…