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 agentmods add skills/tomzx/agents/audit-sdlcnpx 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00023 | $0.02521 |
| Opus 5 | $0.00012 | $0.01260 |
| Sonnet 5 | $0.00005 | $0.00504 |
| Haiku 4.5 | $0.00002 | $0.00252 |
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 3d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit SDLC
Orchestrates multiple audit skills against the project and produces a unified findings report ranked by severity and impact. Optionally feeds the highest-priority findings into issue creation.
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. See ISO/IEC 25010 Quality Model Mapping below for 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.
- 3d ago First seen · 240 lines · 23 tokens per session scan A f9a62549e0c7
audit-sdlc is a skill published in the GitHub repository tomzx/agents (5 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,521 once invoked, about $0.0001 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…