dependency-security-check

dependency-security-check is a skill for Claude Code, Codex from CodeInfinity1/Stram. It costs 24 tokens per session (469 once invoked), scanned A, original, MIT.

A security review skill for examining package installations, dependency changes, scripts, and project manifests. It looks for supply-chain risks before unfamiliar code or packages are used.

In plain words
What is it for?
Use it to inventory dependencies, review approval policies, scan provided files for secrets, and inspect security findings.
Why use it?
It helps identify risky dependencies, install commands, scripts, and possible secret exposure before they affect a project.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to inventory dependencies, review approval policies, scan provided files for secrets, and inspect security findings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/codeinfinity1/stram/dependency-security-check
Install

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.

Any agent
npx skills add CodeInfinity1/Stram --skill dependency-security-check
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for dependency-security-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/codeinfinity1/stram/dependency-security-check/github.svg)](https://agentmods.dev/skills/codeinfinity1/stram/dependency-security-check)
Your own site
<a href="https://agentmods.dev/skills/codeinfinity1/stram/dependency-security-check"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/dependency-security-check/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.

agentmods 80×15 button for dependency-security-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/codeinfinity1/stram/dependency-security-check"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/dependency-security-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 469 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00024 $0.00469
Opus 5.5 $0.00010 $0.00188
Sonnet 5.5 $0.00005 $0.00094
Haiku 4.5 $0.00002 $0.00047

Measured 1mo ago against content hash 8f3b8f90a753, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dependency-security-check 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 1mo 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.

skills/software-engineering/dependency-security-check/SKILL.md · 73 lines

How it starts

The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Dependency Security Check

Purpose

Reduce supply-chain risk when adding or running dependencies. This skill reviews manifests, install commands, package scripts, and trust signals.

When To Use

Use before installing packages, running unfamiliar scripts, adding plugins, updating lockfiles, or executing community skill code.

Inputs And Evidence

  • Package names, manifest diffs, lockfiles, scripts, source repo, version, and requested command.
  • Known vulnerability or audit output when available.

Tool Map

  • dependency_inventory_create
  • secret_scan_report_create
  • approval_policy_review_create
  • security_review_inspect
  • read_file
  • search_workspace
  • run_shell_command
  • skill-security-review
  • secrets-handling

Workflow

  1. Inspect package manifest and scripts.
  2. Use dependency_inventory_create to preserve package, script, trust, and risk evidence.
  3. Use secret_scan_report_create on explicitly provided manifest/config snippets or files when secret leakage risk exists.
  4. Use approval_policy_review_create before install, script execution, or package-manager network actions.
  5. Use security_review_inspect before reporting findings.
  6. Prefer existing dependencies and native implementations.
  7. Request approval before install/network actions.
  8. Verify lockfile and test impact.

Native Implementation Boundaries

  • Do not import external reference audit/Snyk skill code.
  • External scanners require native wrapper or approved shell path.
  • Do not execute package scripts just to inspect them.
  • Native security artifacts are local review documents and do not install packages or run scanners.

Safety And Approval

  • Installs can run code and require approval.
  • Avoid packages with unclear provenance for core agent tools.
  • Do not leak tokens into package manager configs.

Verification

  • Cite manifest/script evidence.
  • Inspect native security artifacts for risk findings and action counts.
  • Report audit/scanner output if run.
  • Confirm no unexpected files changed.

Read the full file on GitHub · 73 lines

Changes

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.

  1. 1mo ago First seen · 73 lines · 24 tokens per session scan A 8f3b8f90a753

Subscribe to this mod's changes

dependency-security-check is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 469 once invoked, about $0.0001 per session on Opus 5.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.

Related

Other skills, from other repositories

android-pentest

A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.

Netw0rkNoob/VulnClaw · 32 tokens

lighting-report-extract

Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.

AlpacaLabsLLC/skills-for-architects · 37 tokens

authentication-patterns

OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.

travisjneuman/.claude · 28 tokens

container-debugging

Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.

WrongStack/WrongStack · 45 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

pr-review

Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…

nitinjain999/platform-skills · 81 tokens