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 agentmods add skills/new1direction/korgex/security-scannpx skills add New1Direction/korgex --skill security-scangit clone --depth 1 https://github.com/New1Direction/korgexWrote 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/new1direction/korgex/security-scan)<a href="https://agentmods.dev/skills/new1direction/korgex/security-scan"><img src="https://agentmods.dev/badge/skills/new1direction/korgex/security-scan.svg" alt="Measured on agentmods" 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 | $0.00034 | $0.00475 |
| Opus 5 | $0.00017 | $0.00237 |
| Sonnet 5 | $0.00007 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
security-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 4d 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.
What it actually says
Verifiable security scan
When you've added or changed dependencies, written code that touches auth, secrets, subprocess calls, file I/O, or the network — or the user asks "is this secure?" — run a security scan before you finish.
How
Use the security_scan tool. It wraps the best scanner on the machine and is
read-only (never modifies files):
- trivy if installed — vulnerabilities, leaked secrets, IaC misconfig, licenses.
- otherwise pip-audit (Python dependency CVEs) or bandit (insecure Python patterns).
Calls:
security_scanwith no args scans the project root.- pass
pathto scan a subtree, orscannerto forcetrivy/pip-audit/bandit.
For the user (or in CI) the same scan is korgex scan [path] — it exits nonzero when a
high/critical finding is present, so it gates a pipeline.
What you get
Each finding has kind (vuln | secret | misconfig | license), severity
(critical → low), id (CVE / rule), target (file or pkg@version), and a fix when
the scanner knows one. The scan is recorded to the verifiable ledger, so findings are
tamper-evident and traceable: korgex why <CVE-or-file> walks a finding back to the
prompt that introduced it, and korgex verify proves the report wasn't edited.
Acting on findings
- Critical / high: fix before finishing — bump the dependency to its
fixversion, remove and rotate the leaked secret, correct the misconfig — then re-scan to confirm it's gone. - False positive: say so explicitly and explain why; don't silently drop it.
- A surfaced secret is compromised. Never commit it; tell the user to rotate it.
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.
- 4d ago First seen · 45 lines · 34 tokens per session scan A fde1fedd7cf7
security-scan is a skill published in the GitHub repository New1Direction/korgex (5 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 475 once invoked, about $0.0002 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.
Other skills, from other repositories
vibe-ui-design
Use when designing UI/UX, defining design systems, choosing color palettes, typography, spacing, or component primitives. Triggers on "design system", "design tokens", "color palette", "UI 设计", "深色工业风", "design language".
vibe-security
Use when performing security audits, vulnerability scanning, dependency checks, or secure code reviews. Triggers on "security audit", "scan vulnerabilities", "安全审查", "漏洞扫描", "OWASP", "dependency check".
vibe-ui-beautify
Use when adding animations, micro-interactions, 3D effects, glassmorphism, or "juicy" tactile feedback to UI components. Triggers on "animation", "hover effect", "transition", "动效", "果汁感", "Framer Motion", "GSAP", "3D 视效".
vibe-plan
Use this skill to create a phased development plan based on requirements, architecture, and API docs.
vibe-test
Use when writing tests, performing unit testing, integration testing, or verifying system functionality. Triggers on "write tests", "run tests", "add unit test", "TDD", "测试", "跑测试".
vibe-autopilot
Use this skill when the user requests fully autonomous, 24/7 hands-free development without human intervention.