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 skills add liuxinye23/CyberStrikeAI --skill vulnerability-assessmentgit clone --depth 1 https://github.com/liuxinye23/CyberStrikeAIWrote 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/liuxinye23/cyberstrikeai/vulnerability-assessment)<a href="https://agentmods.dev/skills/liuxinye23/cyberstrikeai/vulnerability-assessment"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/vulnerability-assessment/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.
<a href="https://agentmods.dev/skills/liuxinye23/cyberstrikeai/vulnerability-assessment"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/vulnerability-assessment.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.01385 |
| Opus 5 | $0.00007 | $0.00692 |
| Sonnet 5 | $0.00003 | $0.00277 |
| Haiku 4.5 | $0.00001 | $0.00138 |
Grade A, and why
vulnerability-assessment 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
漏洞评估
概述
漏洞评估是识别和评估系统漏洞的重要环节。本技能提供漏洞评估的方法、工具和最佳实践。
评估流程
1. 范围确定
确定范围:
- 目标系统
- 网络范围
- 应用范围
- 测试深度
2. 信息收集
收集信息:
- 系统信息
- 网络拓扑
- 服务信息
- 应用信息
3. 漏洞扫描
扫描类型:
- 网络扫描
- 主机扫描
- 应用扫描
- 配置扫描
4. 漏洞验证
验证方法:
- 手动验证
- 工具验证
- 概念验证
- 影响评估
5. 风险评估
评估因素:
- 漏洞严重性
- 利用难度
- 影响范围
- 业务影响
扫描工具
网络扫描
使用Nessus:
# 启动Nessus
# 创建扫描任务
# 配置扫描策略
# 执行扫描
# 分析结果
使用OpenVAS:
# 启动OpenVAS
gvm-setup
# 创建扫描任务
# 执行扫描
# 分析结果
使用Nmap:
# 漏洞扫描
nmap --script vuln target
# 特定漏洞
nmap --script smb-vuln-ms17-010 target
应用扫描
使用Burp Suite:
# 配置代理
# 浏览应用
# 被动扫描
# 主动扫描
# 分析结果
使用OWASP ZAP:
# 启动ZAP
zap.sh
# 快速扫描
zap-cli quick-scan http://target.com
# 完整扫描
zap-cli full-scan http://target.com
使用Acunetix:
# 启动Acunetix
# 创建扫描任务
# 配置扫描选项
# 执行扫描
# 分析结果
代码扫描
使用SonarQube:
# 运行扫描
sonar-scanner
# 分析结果
# 查看报告
使用Checkmarx:
# 使用Web界面
# 上传代码
# 执行扫描
# 分析结果
漏洞分类
按严重性
严重(Critical):
- 远程代码执行
- SQL注入
- 认证绕过
- 敏感数据泄露
高危(High):
- 权限提升
- 信息泄露
- 业务逻辑漏洞
- 配置错误
中危(Medium):
- XSS漏洞
- CSRF漏洞
- 弱密码
- 不安全的配置
低危(Low):
- 信息泄露
- 配置建议
- 最佳实践
- 信息收集
按类型
注入漏洞:
- SQL注入
- 命令注入
- LDAP注入
- XPath注入
认证漏洞:
- 弱密码
- 会话固定
- 认证绕过
- 密码重置
授权漏洞:
- 权限提升
- IDOR
- 水平权限
- 垂直权限
配置错误:
- 默认配置
- 错误配置
- 不安全的存储
- 敏感信息泄露
风险评估
CVSS评分
基础指标:
- 攻击向量(AV)
- 攻击复杂度(AC)
- 所需权限(PR)
- 用户交互(UI)
影响指标:
- 机密性影响(C)
- 完整性影响(I)
- 可用性影响(A)
计算CVSS:
# 使用CVSS计算器
# 输入指标
# 计算分数
# 确定等级
业务影响
评估因素:
- 数据敏感性
- 系统重要性
- 业务影响
- 合规要求
风险矩阵:
低影响 中影响 高影响
高可能性 中 高 严重
中可能性 低 中 高
低可能性 低 低 中
报告编写
报告结构
执行摘要:
- 评估概述
- 关键发现
- 风险评级
- 建议措施
详细发现:
- 漏洞描述
- 影响分析
- 利用步骤
- 修复建议
附录:
- 扫描配置
- 工具版本
- 参考链接
- 术语表
报告模板
# 漏洞评估报告
## 执行摘要
- 评估时间:2024-01-01
- 评估范围:xxx
- 发现漏洞:xx个
- 严重漏洞:x个
## 漏洞列表
### VULN-001: SQL注入
- 严重性:严重
- CVSS评分:9.8
- 描述:...
- 影响:...
- 修复建议:...
## 总结
...
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.
- 11d ago First seen · 305 lines · 14 tokens per session scan A 7d0aacbd12e0
vulnerability-assessment is a skill published in the GitHub repository liuxinye23/CyberStrikeAI (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 14 tokens to every session and 1,385 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…