web-api-audit
Skill1 starsChanged 2 months agoMITView on GitHub
为 REST、GraphQL、WebSocket 和常见 Web 控制设计低影响、单技术、可复核的安全检查;仅使用固定 canary 与 GET/HEAD/OPTIONS。
In this repository11 other files it gives its agents.
- blue-defense-triageSkill
- evidence-hygieneSkill
- full-spectrum-labSkill
- passive-reconSkill
- public-vulnerability-intelSkill
- purple-validationSkill
- qwen-security-copilotSkill
- redteam-orchestratorSkill
- scope-gateSkill
- security-mode-routerSkill
- triage-reportSkill
The file
Files
Web/API audit(Web 与 API 安全审计)
该 skill 只提供测试计划和无害验证框架,不提供任意 payload、绕过技巧、爆破、数据导出或远程执行链。
可选 technique
tls_http_baseline:状态码、响应头、TLS/证书摘要。api_schema_review:对操作者已取得的 OpenAPI/GraphQL 摘要做静态检查。access_control_matrix:设计两个自有测试账号的角色×资源×动作矩阵;不读取真实用户数据。cors_csrf_canary:只做 OPTIONS/GET 的 Origin/方法差异观察。xss_reflection_canary:使用每次唯一的 inert marker;不执行脚本、不持久化。websocket_handshake_review:只审查握手元数据;不发送业务消息。business_logic_sandbox、race_sandbox:仅生成隔离实验室用例,不连接生产系统。
固定控制
- 每次先
scan_plan,再probe_safe(dry_run=true);主动调用需要人工approval_token。 - 每主机串行、至少 1 秒间隔、有限响应字节和 5 秒超时;不跟随越界重定向。
- 禁止 Cookie、Authorization、API key、密码、OOB 回连、真实数据读写、写方法和任意 URL/命令。
- 以响应差异和脱敏证据为依据;只有完整、可复核的影响才进入报告,单纯状态码或版本信息标为
needs_review。
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

