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/sd0xdev/sd0x-harness/dep-auditnpx skills add sd0xdev/sd0x-harness --skill dep-auditgit clone --depth 1 https://github.com/sd0xdev/sd0x-harnessWrote 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/sd0xdev/sd0x-harness/dep-audit)<a href="https://agentmods.dev/skills/sd0xdev/sd0x-harness/dep-audit"><img src="https://agentmods.dev/badge/skills/sd0xdev/sd0x-harness/dep-audit.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.1 | $0.00008 | $0.00750 |
| Opus 5 | $0.00004 | $0.00375 |
| Sonnet 5 | $0.00002 | $0.00150 |
| Haiku 4.5 | $0.00001 | $0.00075 |
Grade A, and why
dep-audit 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 6d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Audit
Trigger
- Keywords: dep audit, dependency audit, security audit dependencies, dep-audit
When NOT to Use
- OWASP code review (use
/codex-security) - Code review (use
/codex-review-fast) - General security review (use
/codex-security)
Workflow Steps
| Step | Goal | Safety |
|---|---|---|
| audit | Scan dependencies for vulnerabilities | read-only |
Failure behavior: report-all
Task
Arguments
$ARGUMENTS
--level <severity>— Minimum reporting level (low/moderate/high/critical), default: moderate--fix— Attempt automatic fix
Step 1: Check for audit script
Use Glob to check if .claude/scripts/dep-audit.sh exists in the project root.
- Found → run:
bash .claude/scripts/dep-audit.sh $ARGUMENTS- If script succeeds, use its output and skip to the Output section.
- If script fails, treat as a real audit failure (do not silently fallback).
- NOT found → skip to Step 2 (do NOT attempt to run the script).
Step 2: Fallback (no audit script)
Detect the project ecosystem and run the audit manually.
Ecosystem detection (check project root for manifest files):
| Manifest | Ecosystem | Audit Command | Fix Command |
|---|---|---|---|
package.json + pnpm-lock.yaml |
Node (pnpm) | pnpm audit --audit-level {LEVEL} |
pnpm audit --fix |
package.json + yarn.lock |
Node (yarn) | yarn audit --level {LEVEL} |
yarn audit --fix or npx yarn-audit-fix |
package.json |
Node (npm) | npm audit --audit-level={LEVEL} |
npm audit fix |
pyproject.toml |
Python | pip-audit or safety check |
pip-audit --fix |
Cargo.toml |
Rust | cargo audit |
cargo audit fix |
go.mod |
Go | govulncheck ./... |
(manual fix) |
build.gradle |
Java | ./gradlew dependencyCheckAnalyze |
(manual fix) |
Default {LEVEL} is moderate unless --level argument is provided.
If --fix is specified, run the fix command for the detected ecosystem after audit.
If no recognized manifest file exists, report an error.
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.
- 6d ago First seen · 100 lines · 8 tokens per session scan A ca15cd00b1be
dep-audit is a skill published in the GitHub repository sd0xdev/sd0x-harness (188 stars, last pushed yesterday), licensed MIT. It adds 8 tokens to every session and 750 once invoked, about $0.0000 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-30.
Other skills, from other repositories
building
Implementation skill for writing production code with TDD. Covers the RED-GREEN-REFACTOR cycle, false-RED detection, vertical slicing, scope escalation, test process discipline, and code generation patterns. Loaded by component-builder and bug-investigator.
diff-driven-docs
Use when a BUILD phase completes, a commit is staged, or a PR is about to be created, and the diff has not yet been reflected in documentation. Also use when the user says "update docs", "sync docs", "document this", or asks whether documentation is up to date.
exploration
Two-mode exploration skill: (1) design dialogue — turn rough ideas into validated designs through collaborative interview before planning; (2) spike — throwaway code answering ONE design question, deleted or absorbed, never shipped. Router invokes mode via dispatch context.
memory-and-handoff
Two-mode skill: (1) session memory — load/persist durable workflow state under .cc10x/ (activeContext, patterns, progress) so context survives compaction; (2) handoff package — portable, secrets-redacted export for a coworker, different tool, or fresh non-cc10x session.
plan-review-gate
Use after saving a non-trivial plan or decision RFC when a fail-closed feasibility, completeness, and alignment review must block execution.
architecture
Greenfield architecture design: map functionality flows, draw components, design APIs, classify dependencies, plan observability. For multi-component, API, schema, auth, or integration-heavy work. For retrofitting existing code, use codebase-hygiene instead.