scan-security

scan-security is a skill for Claude Code from sergeyklay/.agents. It costs 53 tokens per session (2,811 once invoked), scanned A, original, Apache-2.0.

A repository security audit that checks your code for weaknesses and your third-party packages for known risks using Snyk.

In plain words
What is it for?
Use it to scan all files and dependencies, only code, only dependencies, or changes since the last commit. It can apply fixes accepted by the project's build, lint, test, and other checks.
Why use it?
It helps find security problems before they reach users and keeps the review focused on findings the project can safely fix. It also leaves a prioritized report with evidence.

Skill for Claude Code

Written for Claude Code: disable-model-invocation in frontmatter. Also seen: mentions CLAUDE.md; mentions Claude Code; installed under .agents/ (shared by several agents).

Good fit Use it to scan all files and dependencies, only code, only dependencies, or changes since the last commit. It can apply fixes accepted by the project's build, lint, test, and other checks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/sergeyklay/.agents/scan-security
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 sergeyklay/.agents --skill scan-security
Clone the repo
git clone --depth 1 https://github.com/sergeyklay/.agents

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 scan-security

README.md
[![agentmods](https://agentmods.dev/badge/skills/sergeyklay/.agents/scan-security.svg)](https://agentmods.dev/skills/sergeyklay/.agents/scan-security)
Your own site
<a href="https://agentmods.dev/skills/sergeyklay/.agents/scan-security"><img src="https://agentmods.dev/badge/skills/sergeyklay/.agents/scan-security.svg" alt="Measured on agentmods" height="20"></a>
Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,811 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.00053 $0.02811
Opus 5 $0.00026 $0.01406
Sonnet 5 $0.00011 $0.00562
Haiku 4.5 $0.00005 $0.00281

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

Security

Grade A, and why

scan-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 8d 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.

.agents/skills/scan-security/SKILL.md · 174 lines

How it starts

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

Security Audit

Conduct a Snyk security audit of the current repository: static analysis (SAST) of code, software composition analysis (SCA) of dependencies, remediation of findings the project's verification gates accept, and a prioritized evidence-backed findings report.

This skill carries the audit workflow. The project supplies the rest: build / lint / test / install commands, source file conventions, dependency-manager invocations, false-positive patterns, and any hard remediation prohibitions live in the project's context files (AGENTS.md, CLAUDE.md, CONTRIBUTING.md, README.md) and architecture documentation. This skill tells you how to scan, remediate, and report; the project tells you what counts as valid for fixes.

Inputs

The user invokes this skill with an optional scope argument. Resolve the scope before any tool call.

Scope SAST target SCA target
all (default when unset) Entire repository Full dependency manifest set
code Entire repository (skipped)
deps (skipped) Full dependency manifest set
changed Source files modified vs. HEAD Manifest / lock files modified vs. HEAD

For changed, derive the file set from the union of git diff --name-only HEAD and git diff --cached --name-only, deduplicated. Within that set:

  • Source files: pass the diff list to the SAST tool. Snyk Code skips files in unsupported languages. Filter out obvious non-source (lock files, binary assets, generated artifacts) only when their presence in the diff is incidental.
  • Manifest / lock files: the files the project's package manager owns (package.json + lock, go.mod + go.sum, pyproject.toml + lock, Gemfile + Gemfile.lock, composer.json + lock, Cargo.toml + Cargo.lock, etc.). Include only manifests that appear in the diff.

Workflow

Copy this checklist into your response and tick items as you complete them.

  • Step 1 - Pre-flight (capability, auth, build gate, baseline SHA)
  • Step 2 - Static analysis (SAST)
  • Step 3 - Dependency scan (SCA)
  • Step 4 - Triage findings
  • Step 5 - Remediate Fix-Now findings
  • Step 6 - Re-verification scan
  • Step 7 - Report

Read the full file on GitHub · 174 lines

Files

What ships with it

1 file 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.

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. 8d ago First seen · 174 lines · 53 tokens per session scan A bfc43582cc15

Subscribe to this mod's changes

scan-security is a skill published in the GitHub repository sergeyklay/.agents (5 stars, last pushed today), licensed Apache-2.0. It adds 53 tokens to every session and 2,811 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-08-31.