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 skills add CodeInfinity1/Stram --skill dependency-security-checkgit clone --depth 1 https://github.com/CodeInfinity1/StramWrote 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/codeinfinity1/stram/dependency-security-check)<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.
<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>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.00024 | $0.00469 |
| Opus 5.5 | $0.00010 | $0.00188 |
| Sonnet 5.5 | $0.00005 | $0.00094 |
| Haiku 4.5 | $0.00002 | $0.00047 |
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.
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_createsecret_scan_report_createapproval_policy_review_createsecurity_review_inspectread_filesearch_workspacerun_shell_commandskill-security-reviewsecrets-handling
Workflow
- Inspect package manifest and scripts.
- Use
dependency_inventory_createto preserve package, script, trust, and risk evidence. - Use
secret_scan_report_createon explicitly provided manifest/config snippets or files when secret leakage risk exists. - Use
approval_policy_review_createbefore install, script execution, or package-manager network actions. - Use
security_review_inspectbefore reporting findings. - Prefer existing dependencies and native implementations.
- Request approval before install/network actions.
- 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.
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.
- 1mo ago First seen · 73 lines · 24 tokens per session scan A 8f3b8f90a753
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.
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.
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.
authentication-patterns
OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.
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.
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.
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…