Security engineering router for penetration testing, code auditing, red/blue/purple team operations, threat intelligence, and vulnerability research. For specialized application security, cloud security, detection engineering, or security architecture, route to dedicated skills (defending-applications, securing-cloud-and-supply-chain, detecting-and-responding, architecting-security).
npx skills add https://github.com/telagod/code-abyss --skill securing-systems
> 判断先于执行:决定「是否做 / 选什么 / 如何取舍」(栈、方案、架构、权衡)前,先读领域判断内核 skills/_kernel/security/SKILL.md——它管 judgment,本秘典管 execution;冲突时以内核判断为准。
> 安全工程总路由:通用攻防视角与红队 / 蓝队 / 紫队实战知识。
> 专域工作(应用安全防御、云原生加固、检测工程、安全架构)走专门 skill。
> 信级:项目文件 > 标准库 > 训练记忆(标 [unverified])
| 意图 | 秘典 | 核心 |
|------|------|------|
| 渗透测试 | pentest | Web/API/内网、OWASP、BOLA、JWT、GraphQL |
| 代码审计 | code-audit | 危险函数、污点追踪、Source→Sink |
| 红队攻击 | red-team | PoC、C2、横移、免杀、供应链 |
| 蓝队防御 | blue-team | 检测、SOC、IR、取证、密钥轮换 |
| 威胁情报 | threat-intel | OSINT、威胁狩猎、ATT&CK 建模 |
| 漏洞研究 | vuln-research | 逆向、Exploit、Fuzzing、PWN |
| 执行模式 / CTF 沙箱 | authorization-tiers | T1/T2/T3、CTF 目标默认沙箱 |
| 意图 | 走 skill | 适用 |
|------|---------|------|
| 应用层防御(XSS / SQLi / OAuth / LLM AppSec) | defending-applications | 写代码 / 修 CVE / 鉴权设计 |
| 云原生 + 供应链加固 | securing-cloud-and-supply-chain | K8s / CI/CD / SLSA / 云 IAM |
| 检测工程 + 蓝紫队 | detecting-and-responding | Sigma / EDR / IR / 威胁狩猎 |
| 安全架构 + 合规 + 身份 | architecting-security | 威胁建模 / 零信任 / SOC2/PCI |
攻:侦察 → 武器化 → 投递 → 利用 → 安装 → C2 → 行动
守:预防 → 检测 → 响应 → 恢复
紫队:ATT&CK → 红攻 → 蓝检 → 缺口 → 闭环
192.0.2.0/24、198.51.100.0/24)或 example.com<REDACTED>、<TARGET-TOKEN>)| 场景 | 排序 |
|------|------|
| 攻击模拟 | 效果 > 精准 > 控制 |
| 防御响应 | 正确 > 覆盖 > 速度 |
| 紧急事件 | 速度 > 正确 > 简洁 |
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
This skill should be used when the user asks to "perform cloud penetration testing", "assess Azure or AWS or GCP security", "enumerate cloud resources", "exploit cloud misconfigurations", "test O365 security", "extract secrets from cloud environments", or "audit cloud infrastructure". It provides comprehensive techniques for security assessment across major cloud platforms.
You are a dependency security expert specializing in vulnerability scanning, license compliance, and supply chain security. Analyze project dependencies for known vulnerabilities, licensing issues, outdated packages, and provide actionable remediation strategies.
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
This skill should be used when the user asks to "escalate privileges on Linux", "find privesc vectors on Linux systems", "exploit sudo misconfigurations", "abuse SUID binaries", "exploit cron jobs for root access", "enumerate Linux systems for privilege escalation", or "gain root access from low-privilege shell". It provides comprehensive techniques for identifying and exploiting privilege escalation paths on Linux systems.
Expert malware analyst specializing in defensive malware research, threat intelligence, and incident response. Masters sandbox analysis, behavioral analysis, and malware family identification. Handles static/dynamic analysis, unpacking, and IOC extraction. Use PROACTIVELY for malware triage, threat hunting, incident response, or security research.
This skill should be used when the user asks to "use Metasploit for penetration testing", "exploit vulnerabilities with msfconsole", "create payloads with msfvenom", "perform post-exploitation", "use auxiliary modules for scanning", or "develop custom exploits". It provides comprehensive guidance for leveraging the Metasploit Framework in security assessments.
Expert in secure mobile coding practices specializing in input validation, WebView security, and mobile-specific security patterns. Use PROACTIVELY for mobile security implementations or mobile security code reviews.
Take telagod/securing-systems from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.