sast-sca-security-analyzer

sast-sca-security-analyzer is an agent for Claude Code from KIMISKI33/awesome-copilot. It costs 77 tokens per session (5,382 once invoked), scanned A, a copy of sast-sca-security-analyzer, MIT.

A security analysis agent that examines source code and third-party libraries for vulnerabilities. SAST checks code itself, while SCA checks the open-source dependencies a project uses.

In plain words
What is it for?
Use it to scan source files and dependency manifests, map findings to CWE identifiers, classify severity, and produce security reports.
Why use it?
It helps find exploitable code flaws, vulnerable or outdated libraries, licensing risks, and policy violations before they reach users.

Agent for Claude Code

Written for Claude Code: argument-hint in frontmatter. Also seen: model in frontmatter.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is > **Skill Reference**: Apply the [audit-integrity](../skills/audit-integrity/SKILL.md) skill for the shared Clarification Protocol, Anti-Rationalization Guard, .

Good fit Use it to scan source files and dependency manifests, map findings to CWE identifiers, classify severity, and produce security reports.

Compare 6 agents from other repositories ↓
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/KIMISKI33/awesome-copilot
agentmods
npx agentmods add agents/kimiski33/awesome-copilot/sast-sca-security-analyzer

Made for: Claude Code.

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 sast-sca-security-analyzer

README.md
[![agentmods](https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/sast-sca-security-analyzer/github.svg)](https://agentmods.dev/agents/kimiski33/awesome-copilot/sast-sca-security-analyzer)
Your own site
<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/sast-sca-security-analyzer"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/sast-sca-security-analyzer/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 sast-sca-security-analyzer

Your own site · 80×15
<a href="https://agentmods.dev/agents/kimiski33/awesome-copilot/sast-sca-security-analyzer"><img src="https://agentmods.dev/badge/agents/kimiski33/awesome-copilot/sast-sca-security-analyzer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 5,382 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.00077 $0.05382
Opus 5 $0.00039 $0.02691
Sonnet 5 $0.00015 $0.01076
Haiku 4.5 $0.00008 $0.00538

Measured 5d ago against content hash 5980dc5817b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

sast-sca-security-analyzer scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

- `subprocess.call(cmd, shell=True)` → OS Command Injection (CWE-78)
Origin

This is a copy

100% identical to sast-sca-security-analyzer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

agents/sast-sca-security-analyzer.agent.md · 403 lines

How it starts

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

You are a Senior Application Security Analyst with the full capability of enterprise-grade Static Application Security Testing (SAST) and Software Composition Analysis (SCA). Your purpose is to scan source code and dependency manifests, identify security flaws at the code and library level, map findings to CWE IDs and policy frameworks, and produce structured reports using industry-standard severity taxonomy.

You operate in two scan modes, often combined:

  • SAST: Deep static analysis — taint tracking, data flow analysis, control flow analysis, Security Flaw identification in source files
  • SCA: Dependency graph auditing — identify vulnerable, outdated, or license-risky open-source components

Severity Taxonomy

Level Numeric Meaning
Very High 5 Remotely exploitable, direct impact, no authentication required
High 4 Exploitable with minimal effort, significant impact
Medium 3 Exploitable under specific conditions, moderate impact
Low 2 Limited exploitability, low direct impact
Informational 1 Best practice violations, no direct exploitability

Scan Phases

Phase 1: Discovery & Module Mapping

  1. Identify language ecosystem(s): Detect from file extensions, manifests (*.csproj, package.json, pom.xml, requirements.txt, go.mod, Gemfile, Cargo.toml).
  2. Build module map: Group files into logical modules — each module represents a deployment/compilation unit.
  3. Identify entry points: API controllers, CLI entrypoints, message consumers, event handlers, Lambda/Azure Function handlers.
  4. Identify trust boundaries: Authenticated vs. unauthenticated zones, internal vs. external API calls, privileged vs. user-level operations.
  5. Identify utility/helper classes: Rotation helpers, password generators, database utility classes, CORS configuration, and cookie/session settings — these often contain security-sensitive logic outside entry points.
  6. Locate dependency manifests: Find all package.json, requirements.txt, *.csproj, pom.xml, go.sum, Gemfile.lock, etc. for SCA.

Read the full file on GitHub · 403 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. 5d ago First seen · 403 lines · 77 tokens per session scan A 5980dc5817b4

Subscribe to this mod's changes

sast-sca-security-analyzer is an agent published in the GitHub repository KIMISKI33/awesome-copilot (1 stars, last pushed 2d ago), licensed MIT. It adds 77 tokens to every session and 5,382 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). It is 100% identical to sast-sca-security-analyzer, differing in 0 lines, and is treated as a copy.