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 commands/mckruz/claude-code-sdlc/sdlc-audit-artifactsgit clone --depth 1 https://github.com/MCKRUZ/claude-code-sdlcWrote 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/commands/mckruz/claude-code-sdlc/sdlc-audit-artifacts)<a href="https://agentmods.dev/commands/mckruz/claude-code-sdlc/sdlc-audit-artifacts"><img src="https://agentmods.dev/badge/commands/mckruz/claude-code-sdlc/sdlc-audit-artifacts.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.00000 | $0.01560 |
| Opus 5 | $0.00000 | $0.00780 |
| Sonnet 5 | $0.00000 | $0.00312 |
| Haiku 4.5 | $0.00000 | $0.00156 |
Grade A, and why
sdlc-audit-artifacts 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sdlc-audit-artifacts — Artifact Freshness, Impact & History
Audit the content of your pre-Build artifacts: which ones have gone stale relative to the things they depend on, what a change would put at risk, and the full change trail of any one artifact.
This is a sibling to /sdlc-audit, not a replacement. /sdlc-audit audits gate effectiveness
(are the gates well-calibrated). This command audits artifact staleness and change history. They
answer different questions and never overlap.
Everything here is advisory — it surfaces candidates a human dispositions; it never blocks a
gate, changes a verdict, or edits your artifacts, specs, or state.yaml.
Instructions
-
Resolve mode and repo root:
- Workflow mode (default): look for
.sdlc/state.yaml. Pass--state .sdlc/state.yamlto the script. If not found, tell the user to run/sdlc-setupfirst. - Standalone mode (
--repo <path>, or no.sdlc/found): run against any repo containing a.sdlc/directory. History and staleness are only as deep as the ledger in that repo.
- Workflow mode (default): look for
-
Freshen the change-ledger (so staleness reflects what is actually on disk):
uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/audit_artifacts.py record --scan --state .sdlc/state.yamlThis appends only to the change-ledger (
.sdlc/metrics/artifact-log.jsonl) — it hashes the artifact tree and records any new or drifted files. It never touches your artifacts, specs, orstate.yaml. On the very first run it seeds a baseline ("history starts now") — it does not invent a past. In standalone mode pass--repo <path>instead of--state. -
Pick the lens from the user's request:
- Freshness dashboard (default) — per artifact: when it last changed and by whom (from the
ledger), its sign-off status (from
state.yaml), and FRESH or STALE vs. its declared sources. Scope with--phase <id>,--artifact <id|path>, or--since <YYYY-MM-DD>:uv run --project ${CLAUDE_PLUGIN_ROOT}/scripts ${CLAUDE_PLUGIN_ROOT}/scripts/audit_artifacts.py report --state .sdlc/state.yaml
- Freshness dashboard (default) — per artifact: when it last changed and by whom (from the
ledger), its sign-off status (from
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.
- 4d ago First seen · 95 lines · 0 tokens per session scan A 28dcba15bfb8
sdlc-audit-artifacts is a command published in the GitHub repository MCKRUZ/claude-code-sdlc (4 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,560 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.