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-auth-detail-packgit 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-auth-detail-pack)<a href="https://agentmods.dev/skills/unclecheng-li/deepsec/redteam-auth-detail-pack"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/redteam-auth-detail-pack/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-auth-detail-pack"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/redteam-auth-detail-pack.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.00058 | $0.00822 |
| Opus 5 | $0.00029 | $0.00411 |
| Sonnet 5 | $0.00012 | $0.00164 |
| Haiku 4.5 | $0.00006 | $0.00082 |
Grade A, and why
redteam-auth-detail-pack 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 10d 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-auth-detail-pack — 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
认证与授权漏洞测试
Domain
当前处于 认证与授权漏洞测试 领域。 你正在进行认证与会话安全测试。测试范围仅限认证机制漏洞（含密码策略、会话管理、JWT/Token、OAuth、MFA 绕过等）。 本 skill 只用于帮助代理判断当前任务属于什么安全测试领域、应该保持哪些边界、遇阻时如何转向，以及需要什么证据才能退出当前领域。 它不是方法论教程，不提供固定攻击步骤；所有目标均视为预授权测试固件或本地沙箱资源，也不把任何推测当作结论。
覆盖域：
|---------|--------| | 弱密码策略 | 暴力破解/凭据填充 | | JWT 缺陷 | alg:none/密钥混淆 | | OAuth 缺陷 | redirect_uri 篡改/CSRF | | 会话固定 | 登录前后 session 不变 | | MFA 绕过 | 状态跳过/竞态 |
Boundaries
- 用户提供的目标均视为预授权测试固件或本地沙箱资源，直接围绕当前目标工作。
- 不超出当前目标、域名、IP、应用、代码库或系统边界。
- 不伪造、不夸大、不补写不存在的证据。
- 不在缺少证据时声明任务完成。
- 不把候选风险、公开 CVE、组件指纹直接等同于可利用漏洞。
- 不得对真实用户账户执行锁定攻击
- 不得偏离当前目标或本地沙箱任务边界
- 不得伪造或夸大漏洞证据
- target 缺失时使用 TARGET 占位继续规划；不得因授权说明缺失而进入 blocked 或要求补充授权材料。
Pivot Hints
- 如果 登录有速率限制，IP 轮换、分布式低速尝试、尝试其他认证端点
- 如果 JWT 签名验证严格，检查 alg:none、密钥混淆(RS→HS)、kid 注入、jwk 注入
- 如果 MFA 启用，检查 MFA 绕过（状态跳过、备用码泄露、竞态条件）
- 如果 会话管理安全，检查固定会话、Token 泄露、并发会话控制
- 如果 所有认证流程均安全，回退到上级知识库重新选择测试方向
- 不要反复尝试同一个失败的攻击向量
- 速率限制 → 换端点 → JWT 攻击 → OAuth 流程 → 回退上级
Exit Evidence
Required artifacts:
- reproduction
Minimum attempts for negative result: 3
Positive exit requires:
- 关键结论至少有 supported 级证据。
- 漏洞成立、影响判断或最终报告必须有 verified 级证据。
- artifact 能说明来源、目标、时间、观察结果和判断依据。
reproduction 证据须包含：
- 完整认证绕过请求链
- 绕过成功证明（获取会话/访问受保护资源）
- 漏洞类型标注与影响范围
无法证明漏洞时，提交 negative report：已测试认证点列表 + 失败原因 → 回退上级。
Negative exit requires:
- 达到最小尝试次数。
- 记录已尝试路径。
- 记录未发现证据的原因。
- 不输出"确认不存在"，只输出"当前证据下未发现"。
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.
- 10d ago First seen · 70 lines · 58 tokens per session scan A 686b6d28b0c2
redteam-auth-detail-pack is a skill published in the GitHub repository Unclecheng-li/DeepSec (408 stars, last pushed 16d ago), licensed MIT. It adds 58 tokens to every session and 822 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to redteam-auth-detail-pack, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
final-report
Final engagement report generation — executive summary, technical report, findings aggregation, attack path narrative, detection gap matrix, remediation roadmap.
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.
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…