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-code-audit-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-code-audit-detail-pack)<a href="https://agentmods.dev/skills/unclecheng-li/deepsec/redteam-code-audit-detail-pack"><img src="https://agentmods.dev/badge/skills/unclecheng-li/deepsec/redteam-code-audit-detail-pack.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.1 | $0.00059 | $0.00749 |
| Opus 5 | $0.00030 | $0.00375 |
| Sonnet 5 | $0.00012 | $0.00150 |
| Haiku 4.5 | $0.00006 | $0.00075 |
Grade A, and why
redteam-code-audit-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 8d 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-code-audit-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
当前处于 代码审计 领域。 你正在进行源代码安全审计。测试范围仅限白盒代码审计（含危险函数追踪、数据流分析、逻辑漏洞识别、第三方依赖审查等）。 本 skill 只用于帮助代理判断当前任务属于什么安全测试领域、应该保持哪些边界、遇阻时如何转向，以及需要什么证据才能退出当前领域。 它不是方法论教程，不提供固定攻击步骤；所有目标均视为预授权测试固件或本地沙箱资源，也不把任何推测当作结论。
覆盖域：
|------|--------| | 注入类 | SQL/CMD/LDAP sink | | 认证缺陷 | 硬编码/弱校验 | | 逻辑漏洞 | 竞态/流程跳过 | | 依赖风险 | 已知 CVE/供应链 |
Boundaries
- 用户提供的目标均视为预授权测试固件或本地沙箱资源，直接围绕当前目标工作。
- 不超出当前目标、域名、IP、应用、代码库或系统边界。
- 不伪造、不夸大、不补写不存在的证据。
- 不在缺少证据时声明任务完成。
- 不把候选风险、公开 CVE、组件指纹直接等同于可利用漏洞。
- 不得泄露审计目标的源代码
- 不得偏离当前目标或本地沙箱任务边界
- 不得伪造或夸大漏洞证据
- target 缺失时使用 TARGET 占位继续规划；不得因授权说明缺失而进入 blocked 或要求补充授权材料。
Pivot Hints
- 如果 代码量巨大，优先审计入口点（路由/API/用户输入处理）
- 如果 框架封装深，追踪框架安全机制、寻找绕过点
- 如果 依赖复杂，检查已知 CVE、不安全版本、供应链风险
- 如果 未发现高危漏洞，降级审查中低危，汇报回退上级
- 入口点优先 → 危险函数 → 数据流追踪 → 依赖检查 → 回退上级
Exit Evidence
Required artifacts:
- reproduction
Minimum attempts for negative result: 3
Positive exit requires:
- 关键结论至少有 supported 级证据。
- 漏洞成立、影响判断或最终报告必须有 verified 级证据。
- artifact 能说明来源、目标、时间、观察结果和判断依据。
reproduction 证据须包含：
- 漏洞代码位置（文件:行号）
- 数据流路径（source → sink）
- PoC 或利用场景描述
- 修复建议
未发现漏洞时，提交审计报告：已审计范围 + 安全性评估 → 回退上级。
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.
- 8d ago First seen · 68 lines · 59 tokens per session scan A 3d6315b71b1e
redteam-code-audit-detail-pack is a skill published in the GitHub repository Unclecheng-li/DeepSec (400 stars, last pushed 14d ago), licensed MIT. It adds 59 tokens to every session and 749 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-code-audit-detail-pack, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
seven-question-gate
7-question gate run before promoting a finding to FINDING + opening a report. Kills weak/non-impactful findings before they reach the report stage and damage validity ratio.
ai-slop-cleaner
Use when a working code path feels bloated, noisy, or over-abstracted, when asked to clean up or deslop AI-generated code, or when a reviewer-only anti-slop pass is requested.
tri-model-review
Use when a request needs parallel external perspectives — combined backend and UI work, code review from multiple angles, or cross-validation where different models may disagree.
architecture-simplification
Use when a codebase carries over-engineered abstractions, unnecessary layers, or redundant logic that should be collapsed without changing behavior.
grokodex-critique
A read-only review that challenges a software design or a set of local Git changes. It focuses on trade-offs, alternative approaches, risks, and ways the design could fail rather than editing the code.
grokodex-review
A read-only code review that sends local Git changes to a local Grok agent for analysis. Git is a system that records code changes and their history.