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 security-headers-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/security-headers-review)<a href="https://agentmods.dev/skills/liuxinye23/cyberstrikeai/security-headers-review"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/security-headers-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/security-headers-review"><img src="https://agentmods.dev/badge/skills/liuxinye23/cyberstrikeai/security-headers-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.00029 | $0.00688 |
| Opus 5 | $0.00015 | $0.00344 |
| Sonnet 5 | $0.00006 | $0.00138 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
security-headers-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 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.
What it actually says
安全响应头与浏览器边界审计
何时使用
当目标是 Web 站点、管理后台、单页应用、下载中心或含跨域访问的 API 时使用本技能。
快速流程
- 抽样首页、登录页、后台页、静态资源、下载接口、API 接口。
- 对比各路径的安全头是否一致，尤其是登录态与匿名态差异。
- 检查 CSP、CORS、缓存头、点击劫持保护、HSTS 与浏览器隔离头。
- 结合业务上下文判断“缺失”与“配置不当”哪个更关键。
重点检查
内容安全与脚本执行
- CSP 是否真实生效，还是仅在部分页面存在。
- 是否过度依赖宽松来源、内联脚本豁免或过大的第三方域范围。
跨域与跨源
- CORS 是否按资源粒度配置，而不是对敏感接口统一放宽。
- 是否把认证态接口与宽松跨域策略叠加。
传输与缓存
- HSTS 是否仅在 HTTPS 主入口存在，子域策略是否明确。
- 登录页、个人中心、下载接口、导出接口的缓存控制是否合适。
UI 与隔离
- 点击劫持防护是否覆盖后台与支付、配置、审批等敏感页面。
- 浏览器隔离头是否与应用行为匹配，避免只在首页配置。
建议工具
http-framework-test
- 重点看响应头、重定向链、缓存行为和不同页面的头部差异。
- 分别抓匿名态、登录态和高权限态页面。
nuclei
- 用于补充常见头部缺失与明显错配的模板检测。
证据要求
- 保存关键路径的完整响应头摘要。
- 若问题仅出现在某一路由或某一角色，明确写出适用范围。
- 不要只报“缺少某头”，要解释其在该业务中的真实影响。
修复建议方向
- 按页面与资源类型制定头部基线，而不是全站复制一份配置。
- 对登录态页面优先收紧缓存、点击劫持与跨域策略。
- 对 CSP、HSTS、CORS 做渐进式验证和回归检查。
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 · 90 lines · 29 tokens per session scan A 70bdccad7c5a
security-headers-review is a skill published in the GitHub repository liuxinye23/CyberStrikeAI (0 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 29 tokens to every session and 688 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…