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.
git clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/security-dependencies)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/security-dependencies"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/security-dependencies/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/commands/kumaran-is/claude-code-onboarding/security-dependencies"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/security-dependencies.svg" alt="Reviewed on agentmods" width="80" 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.00052 | $0.01805 |
| Opus 5 | $0.00026 | $0.00903 |
| Sonnet 5 | $0.00010 | $0.00361 |
| Haiku 4.5 | $0.00005 | $0.00180 |
Grade A, and why
security-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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dependency Vulnerability Scanner
Scan project dependencies across multiple ecosystems to identify vulnerabilities, generate an SBOM, and provide risk-weighted prioritization.
Arguments
$ARGUMENTS
Instructions
Step 1: Determine scan path and detect ecosystems
SCAN_PATH="${1:-.}"
echo "========================================="
echo "DEPENDENCY VULNERABILITY SCAN"
echo "========================================="
echo "Scanning: $SCAN_PATH"
echo ""
echo "--- Ecosystem Detection ---"
HAS_NPM=false
HAS_PIP=false
HAS_MAVEN=false
HAS_PUB=false
[ -f "$SCAN_PATH/package.json" ] && HAS_NPM=true && echo " npm ecosystem detected (package.json)"
[ -f "$SCAN_PATH/pyproject.toml" ] || [ -f "$SCAN_PATH/requirements.txt" ] && HAS_PIP=true && echo " pip ecosystem detected"
[ -f "$SCAN_PATH/pom.xml" ] && HAS_MAVEN=true && echo " Maven ecosystem detected (pom.xml)"
[ -f "$SCAN_PATH/pubspec.yaml" ] && HAS_PUB=true && echo " pub.dev ecosystem detected (pubspec.yaml)"
if [ "$HAS_NPM" = false ] && [ "$HAS_PIP" = false ] && [ "$HAS_MAVEN" = false ] && [ "$HAS_PUB" = false ]; then
echo " No supported ecosystems detected. Supported: npm, pip, Maven, pub.dev"
echo " Ensure $SCAN_PATH contains package.json, pyproject.toml, requirements.txt, pom.xml, or pubspec.yaml."
exit 1
fi
echo ""
Step 2: Run ecosystem-specific scanners
npm (NestJS / Angular)
if [ "$HAS_NPM" = true ]; then
echo "--- npm Audit ---"
cd "$SCAN_PATH"
if ! command -v npm &>/dev/null; then
echo " [SKIP] npm not found. Install Node.js: https://nodejs.org/"
else
if command -v jq &>/dev/null; then
npm audit --json 2>/dev/null | jq '.vulnerabilities | to_entries[] | {name: .key, severity: .value.severity, cvss: .value.cvss.score, fixAvailable: .value.fixAvailable}' 2>/dev/null || echo " No vulnerabilities found or npm audit not available."
else
npm audit 2>/dev/null | grep -E "CRITICAL|HIGH|MODERATE|LOW" || echo " No vulnerabilities found or npm audit not available."
echo " [NOTE] Install jq for structured JSON output: https://jqlang.github.io/jq/"
fi
fi
echo ""
fi
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.
- 5d ago First seen · 196 lines · 52 tokens per session scan A 808f8ca225fd
security-dependencies is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 52 tokens to every session and 1,805 once invoked, about $0.0003 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-09-03.
Other commands, from other repositories
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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.