pentest-verification
Skill19 starsChanged 2 months agoApache-2.0View on GitHub
验证铁律:搜索≠漏洞,confirmed Fact须证据,tentative表线索,禁止空泛推测,负结果也落库, 想象力拉满+单步验证零容忍。Use when writing project facts, validating findings, or avoiding hallucination.
2 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- AIPentest/CyberStrikeAIedited, first seen Nov 3, 2026
- Ed1s0nZ/CyberStrikeAIedited, first seen Nov 3, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 2
- AIPentest/CyberStrikeAI★ 8.5k96% same
- Ed1s0nZ/CyberStrikeAI★ 8.5k96% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- active-directory-attackSkill
- ai-llm-app-attackSkill
- attack-surface-reconSkill
- binary-mobile-reversingSkill
- blockchain-contract-attackSkill
- capability-primitive-searchSkill
- cloud-attack-methodsSkill
- component-vuln-intelSkill
- cyberstrike-eino-demoSkill
- experience-closeoutSkill
- handoff-persistence-c2Skill
- initial-access-phishingSkill
- local-corpus-cveSkill
- pentest-agent-osSkill
- pentest-blackboardSkill
- pentest-output-standardsSkill
- post-exploitationSkill
- proxy-tool-bootstrapSkill
- redteam-opsecSkill
- source-code-huntingSkill
- specialized-attack-playbooksSkill
- unlimited-attack-scopeSkill
- web-attack-methodsSkill
- wireless-hardware-attackSkill
- zero-day-discoverySkill
The file
Files
验证铁律（全系统最高规则，违反即幻觉）
1. 搜索结果 ≠ 漏洞。公开情报/PoC线索不可直接 record_vulnerability，也不可写 confidence=confirmed；
可写 tentative 的 note/finding 线索，或只留本轮待验证方向，验证后再落库。
本地 zvec 命中的 CVE 描述 = 公开记录，不是验证证据。
可以写 tentative 的 intel/ Fact，不能直接 confirmed，也不能单凭描述 record_vulnerability。
2. 每个 confirmed Fact 必须在 body（或关联漏洞 POC）附验证证据:命令输出/HTTP响应/文件内容/回连记录。
3. 禁止"可能/疑似/推测XX" —— 要么确认+证据写 Fact/漏洞，要么 tentative 标明线索，要么不报。
4. 验证失败 → 写负结果 Fact("测了XX,无可利用漏洞")，用 upsert_project_fact 落库，防止重复尝试。
5. 想象力拉满(敢想全网没人串过的链),单步验证零容忍(每段用真实证据钉死后再 confirmed)。与黑板工具对齐见 pentest-blackboard。
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.