sec-scan

sec-scan is a command for coding agents from atuljha23/holocron. It costs 27 tokens per session (443 once invoked), scanned A, original, MIT.

A security check for changed code, including searches for exposed secrets, known vulnerable dependencies, and common coding mistakes. SAST means checking source code for security flaws without running the application.

In plain words
What is it for?
Use it on a working-tree diff or selected changes to review authentication, injection, sessions, cryptography, and returned data.
Why use it?
It can catch credentials accidentally committed, reported dependency vulnerabilities, and issues such as injection or weak authentication before code is merged.

Command

Part of the holocron plugin — 11 skills, 24 commands, 14 agents, 6 hooks shipped together

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.

agentmods
npx agentmods add commands/atuljha23/holocron/sec-scan
Clone the repo
git clone --depth 1 https://github.com/atuljha23/holocron

Or install holocron, the plugin that ships this one along with the rest of its 11 skills, 24 commands, 14 agents, 6 hooks.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/atuljha23/holocron/sec-scan.svg)](https://agentmods.dev/commands/atuljha23/holocron/sec-scan)
Your own site
<a href="https://agentmods.dev/commands/atuljha23/holocron/sec-scan"><img src="https://agentmods.dev/badge/commands/atuljha23/holocron/sec-scan.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 443 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00027 $0.00443
Opus 5 $0.00014 $0.00221
Sonnet 5 $0.00005 $0.00089
Haiku 4.5 $0.00003 $0.00044

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

Security

Grade A, and why

sec-scan 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 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.

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.

commands/sec-scan.md · 46 lines

What it actually says

/holocron:sec-scan

Target: $ARGUMENTS — or working-tree diff if no arg.

1. Secret sweep

Run the regex gauntlet across the diff:

git diff $ARGUMENTS | grep -E 'AKIA[0-9A-Z]{16}|ghp_[A-Za-z0-9]{36,}|xox[baprs]-|AIza[0-9A-Za-z_-]{35}|sk_live_|sk-ant-|-----BEGIN .*PRIVATE KEY-----'

If anything matches, stop and report. Do not echo the matched secret in your output — redact.

2. Dependency advisories

Detect ecosystem and run the native auditor. Skip if the tool isn't installed.

  • Node: npm audit --audit-level=high (or pnpm/yarn equivalent)
  • Python: pip-audit if present
  • Ruby: bundler-audit check --update if present
  • Rust: cargo audit if present
  • Go: govulncheck ./... if present

Summarize high/critical advisories. Ignore dev-only nuisance advisories unless severe.

3. SAST pass

Delegate to @security-reviewer with the diff and ask for:

  • Authn/authz gaps
  • Injection surfaces (SQL, shell, template, path, deserializer)
  • Session / cookie attribute issues
  • Unsafe crypto (MD5/SHA1 for security, ECB mode, custom crypto)
  • Over-returning in response objects

Output

Severity-ordered findings (Critical / High / Medium / Low), each with file:line, impact, trigger, fix. Redact any actual secrets found.

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 · 46 lines · 27 tokens per session scan A ce11e7d483af

Subscribe to this mod's changes

sec-scan is a command published in the GitHub repository atuljha23/holocron (2 stars, last pushed 4mo ago), licensed MIT. It adds 27 tokens to every session and 443 once invoked, about $0.0001 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.