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 secret-exposure-reviewgit 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/secret-exposure-review)<a href="https://agentmods.dev/skills/liuxinye23/cyberstrikeai/secret-exposure-review"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/secret-exposure-review/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/secret-exposure-review"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/secret-exposure-review.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.00032 | $0.00750 |
| Opus 5 | $0.00016 | $0.00375 |
| Sonnet 5 | $0.00006 | $0.00150 |
| Haiku 4.5 | $0.00003 | $0.00075 |
Grade A, and why
secret-exposure-review 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.
What it actually says
密钥与敏感配置暴露审计
何时使用
当目标包含前端构建产物、公开配置文件、移动端接口、备份资源、历史路径或第三方集成配置时，使用本技能。
快速流程
- 枚举静态资源、构建产物、配置文件、历史 URL 和备份命名模式。
- 审阅是否存在真实 API Key、访问令牌、Webhook 密钥、数据库连接串、调试开关。
- 区分“公开标识符”和“可直接滥用的秘密”，避免误报。
- 记录暴露位置、可见范围、是否仍有效、可到达的后端资源。
重点检查
前端与静态资源
main.*.js、配置 JSON、Source Map、调试页面、运行时环境变量回显。- 第三方 SDK 初始化参数中，哪些只是公开站点标识，哪些是真正私密凭据。
备份与历史路径
- 常见备份命名、旧版本入口、临时导出文件、测试目录、历史快照。
- 历史 URL 中暴露的旧配置、旧接口或已下线资源是否仍可访问。
错误响应与日志
- 调试堆栈、代理错误页、集成失败提示、诊断面板是否回显敏感字段。
- 是否在响应头、下载文件名、注释或示例代码中泄露内部标识。
建议工具
http-framework-test
- 拉取首页、关键 JS、配置路径、错误路径并保存响应头与正文摘要。
- 对静态资源使用只读方式检查，不做修改型验证。
nuclei
- 用于补充常见敏感文件、备份扩展名、默认配置暴露模板。
gau / waybackurls
- 从历史路径中找回旧资源、旧配置、旧后台入口，再回源验证是否仍在线。
证据要求
- 记录暴露位置、响应状态、片段摘要和失效时间判断依据。
- 若为真实秘密，只展示脱敏前后缀，不直接写完整值。
- 写清楚该秘密的潜在影响范围，而不是只说“存在 key”。
修复建议方向
- 把真实秘密移出前端与公开资源。
- 对备份、历史产物、Source Map 和调试页做访问控制或下线清理。
- 对第三方集成区分公开标识符与私密凭据，避免混用。
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 · 92 lines · 32 tokens per session scan A 626cb697c9e0
secret-exposure-review is a skill published in the GitHub repository liuxinye23/CyberStrikeAI (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 32 tokens to every session and 750 once invoked, about $0.0002 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…