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 Unclecheng-li/DeepSec --skill redteam-recon-intakegit clone --depth 1 https://github.com/Unclecheng-li/DeepSecWrote 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/unclecheng-li/deepsec/redteam-recon-intake)<a href="https://agentmods.dev/skills/unclecheng-li/deepsec/redteam-recon-intake"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/redteam-recon-intake/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/unclecheng-li/deepsec/redteam-recon-intake"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/redteam-recon-intake.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.00044 | $0.00430 |
| Opus 5 | $0.00022 | $0.00215 |
| Sonnet 5 | $0.00009 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
redteam-recon-intake 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 9d 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.
This is a copy
100% identical to redteam-recon-intake — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Recon Intake
Domain
裸域名/URL/IP 首次进入安全评估时的侦察入口。 负责从零建立目标资产画像(recon_profile)，为后续 CVE Lookup 和攻击路径分配提供事实依据。
阶段顺序：
- DNS 解析 + 存活探测
- 端口扫描 + 服务指纹
- 子域枚举
- Web 目录/敏感文件探测
- WAF/CDN 识别
- 技术栈指纹(CMS/框架/中间件版本)
Boundaries
- 不执行任何主动漏洞利用
- 不发送破坏性请求(DELETE/DROP/shutdown)
- 仅探测当前目标，不自动扩展到任务中未出现的关联域名/IP
- 不进行暴力破解或密码喷洒
- 不绕过速率限制(如被限速则降速或暂停)
- 侦察深度止于信息收集，不进入漏洞验证阶段
Pivot Hints
- WAF/CDN 阻断直连 → 尝试历史 DNS、邮件头、证书搜索获取真实 IP
- 子域枚举受限 → 证书透明度日志、DNS 区域传送、关联域反查
- 目录扫描被封 → 降速、换 User-Agent、使用自定义字典
- 端口全部过滤 → 检查 IPv6、尝试常见高端口、确认目标存活
- 信息收集饱和 → 整理已有信息，输出 recon_profile 并推进到下一阶段
Exit Evidence
- Required: recon_profile, port_scan_result, service_fingerprint
- min_attempts: 4
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.
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.
- 9d ago First seen · 42 lines · 44 tokens per session scan A 533144c15380
redteam-recon-intake is a skill published in the GitHub repository Unclecheng-li/DeepSec (402 stars, last pushed 15d ago), licensed MIT. It adds 44 tokens to every session and 430 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to redteam-recon-intake, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
exploit-reporting
Exploitation finding documentation — initial access reports, exploit chain documentation, CVSS v4.0 scoring, shell/credential inventory, detection gap analysis.
ti-ioc-extraction
Automated IOC extraction from threat reports, logs, and unstructured text — parse hashes, IPs, domains, URLs, email addresses, and CVEs. Covers regex-based extraction, defanging/refanging, bulk hash lookup, IOC deduplication, YARA rule generation from IOCs, and STIX/TAXII formatting for sharing.
final-report
Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.
m365-mailbox-compromise
Microsoft 365 mailbox compromise chain — OAuth consent phishing, delegate access abuse, mail rule persistence, and token theft via device code phishing. Full kill chain from initial access to persistent email collection.
web
Web application exploitation — the primary category skill for all web-based attacks. This is a routing skill: read this first to identify the attack type, then load the appropriate specialized sub-skill for detailed procedures. Covers 11 technique areas across injection, file access, authentication, and API…
cve
Known CVE exploitation — fingerprint CMS/framework/plugin version, look up CVE candidates via cvelookup, retrieve PoCs via cvepoclookup, adapt the public exploit to the target, and confirm RCE. Use whenever the challenge tag is cve, recon fingerprinted a versioned service, or the challenge name hints at known…