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/parkerm2/create-claude-workflow/audit-dependenciesgit clone --depth 1 https://github.com/ParkerM2/create-claude-workflowWrote 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/parkerm2/create-claude-workflow/audit-dependencies)<a href="https://agentmods.dev/commands/parkerm2/create-claude-workflow/audit-dependencies"><img src="https://agentmods.dev/badge/commands/parkerm2/create-claude-workflow/audit-dependencies.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.00018 | $0.04545 |
| Opus 5 | $0.00009 | $0.02273 |
| Sonnet 5 | $0.00004 | $0.00909 |
| Haiku 4.5 | $0.00002 | $0.00455 |
Grade A, and why
audit-dependencies 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 — 547 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit Dependencies Workflow
Comprehensive dependency scanning for CVEs, outdated packages, license compliance, and staleness. Auto-creates Jira tickets for critical vulnerabilities with remediation guidance.
Integration Points
- Jira MCP: Auto-create tickets for CVEs, link to tickets for tracking
- GitHub Advisory Database: CVE lookup via web search/APIs
- Package Managers: Native audit tools (npm, pip, cargo, etc.)
- Memory: Audit history, dependency tracking, remediation status
- Slack MCP: Vulnerability notifications
Workflow Phases
Phase 1: Project Detection (Type & Lock File Identification)
Identify project type and read dependency manifests:
-
Detect Project Type
- Check for manifest files in priority order:
- Node.js:
package.json+package-lock.jsonoryarn.lock - Python:
requirements.txt,Pipfile,pyproject.toml+Pipfile.lockorpoetry.lock - Rust:
Cargo.toml+Cargo.lock - Go:
go.mod+go.sum - Java:
pom.xml(Maven) +pom.lockorbuild.gradle+gradle.lock - Ruby:
Gemfile+Gemfile.lock - PHP:
composer.json+composer.lock
- Node.js:
- Store detected type:
memory/project-type.yaml
- Check for manifest files in priority order:
-
Read Lock Files
- Parse lock file for exact versions (not ranges from manifest)
- Build dependency list:
dependencies: express: 4.18.2 (direct) accepts: 1.3.8 (transitive) cookie: 0.5.0 (transitive) - Identify: direct vs. transitive (nested), pinned versions
-
Monorepo Detection
- If multiple package files:
workspace/services/api/package.json,workspace/ui/package.json - Scan all:
find . -name "package.json" -not -path "*/node_modules/*" - Flag: "Monorepo detected; scanning N independent projects"
- Process each separately or aggregate (configurable)
- If multiple package files:
-
Extract Metadata
- Project name, version, description
- Dev vs. production dependencies (if available)
- Private vs. public packages
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 · 547 lines · 18 tokens per session scan A 4f0a3631968f
audit-dependencies is a command published in the GitHub repository ParkerM2/create-claude-workflow (4 stars, last pushed 5mo ago), licensed MIT. It adds 18 tokens to every session and 4,545 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 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.