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 JustineDevs/premortem --skill sca-securitygit clone --depth 1 https://github.com/JustineDevs/premortemWrote 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/justinedevs/premortem/sca-security)<a href="https://agentmods.dev/skills/justinedevs/premortem/sca-security"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/sca-security/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/justinedevs/premortem/sca-security"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/sca-security.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.00137 | $0.03068 |
| Opus 5 | $0.00068 | $0.01534 |
| Sonnet 5 | $0.00027 | $0.00614 |
| Haiku 4.5 | $0.00014 | $0.00307 |
Grade A, and why
sca-security 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 9d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Software Composition Analysis (SCA)
Router skill for dependency security: SBOM generation, multi-source vuln correlation, license compliance, supply chain review, and reachability-driven triage. Optimized for polyglot repositories and PR-time lockfile review. Load the relevant workflow + ecosystem reference on demand — do not read the whole skill up front.
When to Use
- Scanning project dependencies for known vulnerabilities (CVE / GHSA / OSV)
- Generating an SBOM (CycloneDX or SPDX) for a repo, container, or binary
- Reviewing a PR's lockfile delta for new vulns, license changes, malicious packages
- Reachability analysis to prioritize the 5-15% of findings that are actually exploitable
- License compliance against an allow/deny policy
- Supply chain review: typosquatting, dependency confusion, malicious package triage
- Ecosystem-specific audits: npm, yarn, pnpm, pip, poetry, Maven, Gradle, Go, Cargo, Ruby, Composer
- CI/CD integration for continuous dependency scanning
Trigger Phrases
- "scan dependencies", "check package vulnerabilities", "run npm audit"
- "generate SBOM", "CycloneDX", "SPDX"
- "license compliance", "audit licenses"
- "supply chain", "typosquat", "dependency confusion", "malicious package"
- "lockfile diff", "dep review", "PR dependency review"
- "is this CVE reachable", "reachability analysis", "filter false positives"
When NOT to Use This Skill
- First-party source code vulnerabilities (SQLi, XSS, SSRF, etc.) → use
sast-orchestration. SCA looks at third-party deps only. - OS-level packages inside container images (apt, apk, rpm) → use
container-security. (Overlap: Syft/Grype handle both; choose based on where the bulk of the work is.) - Infrastructure-as-Code misconfigurations (Terraform, K8s YAML) → use
iac-security. - Live web-app runtime testing → use
dast-automation. - LLM-specific supply chain (model weights, prompts, tool chains) → use
llm-security. - Mobile app third-party libraries → this skill works, but
android-pentest/ios-pentestadd platform context (cocoapods, SPM, gradle android).
What ships with it
19 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/bounty_patterns_2024_2026.md 7.9 KB
- references/cargo.md 3.6 KB
- references/go_modules.md 4.3 KB
- references/malicious_package_indicators.md 5.2 KB
- references/maven_gradle.md 4.1 KB
- references/npm_yarn_pnpm.md 3.8 KB
- references/php_composer.md 3.0 KB
- references/python_pip_poetry.md 4.2 KB
- references/ruby_gems.md 2.4 KB
- references/sbom_formats.md 4.2 KB
- references/vuln_databases.md 4.0 KB
- schemas/finding.json 3.7 KB
- templates/sca_report.md 2.0 KB
- workflows/license_audit.md 3.1 KB
- workflows/lockfile_diff.md 4.5 KB
- workflows/reachability_analysis.md 6.3 KB
- workflows/sbom_generation.md 2.8 KB
- workflows/supply_chain_review.md 5.1 KB
- workflows/vuln_correlation.md 3.4 KB
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.
- 9d ago First seen · 202 lines · 137 tokens per session scan A 5f2ef842b531
sca-security is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 137 tokens to every session and 3,068 once invoked, about $0.0007 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 skills, from other repositories
critique
Expertise in auditing and fixing repository scripts and GitHub Actions workflows to ensure technical robustness and security.
atmos-version
Atmos Version Tracker: version tracks, lock files, managed external dependency versions, atmos version track commands, !version, file managers, update policy, pinning, and CI verification.
jenkins
Jenkins CI/CD integration for investigating builds, deployments, pipeline stages, and test results during RCA.
github-actions
Use when authoring or fixing GitHub Actions CI/CD — workflows under .github/workflows, triggers, job matrix, caching, token permissions, OIDC cloud deploys, environment gates, reusable workflows. NOT the Dockerfile or image build strategy (that is docker), NOT the branching model (that is git-workflow), NOT release…
neon
Use when you have picked Neon (serverless Postgres) and need to connect correctly from a serverless or edge runtime, wire database branching into dev, preview and CI, or stop being burned by scale-to-zero cold starts and pooler limits — including choosing HTTP versus WebSocket connections and pooled versus direct…
hatch3r-gh-agentic-workflows
Sets up CI/CD agentic workflows for continuous AI-powered repository automation (GitHub Actions, Azure Pipelines, GitLab CI).