본문으로 건너뛰기
cccskills
무료GitHub에 공개

triage

Finding validation gate - 7-Question triage adapted for FIND schema. Run before moving any FIND from Research to Completed. One NO = keep in Research. All YES = move to Completed, then run /evidence.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH
설치 방법 보기

포함된 파일(1)

  • SKILL.md3.3 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Triage: Finding Validation Gate

Use BEFORE moving any FIND from Vulns/Research/ to Vulns/Completed/.

One wrong answer = keep the finding in Research. Move on to next test class.

THE 7-QUESTION GATE

Ask in order. One NO = STOP for this finding.

Q1: Can an attacker use this RIGHT NOW, step by step?

Complete this template:

Setup:   I need [own account / another user's ID / no account / internal access]
Request: [exact HTTP method, URL, headers, body -- copy-paste ready]
Result:  I can [read / modify / delete / execute] [exact data or action]
Impact:  The real-world consequence is [specific impact]

If you CANNOT write the Request line as a real reproducing command -> keep in Research.

Q2: Is the impact within engagement scope?

  • Does it affect an in-scope asset?
  • Does the impact match the severity level being claimed?
  • Not a third-party service the target merely uses?

Q3: Is the root cause in an in-scope asset?

  • Production asset (not staging/dev unless in scope)
  • Not out-of-scope subsidiary or third-party

Q4: Does it require privileged access that an attacker cannot realistically obtain?

  • "Admin can do X" = not a finding
  • "Non-admin can do X that only admin should do" = valid
  • Pre-auth or low-auth is highest value

Q5: Is this already known or documented?

  • Check Vuln-index.md - not already listed?
  • Check Deadends.md - not already investigated and closed?
  • Not design-documented behaviour?

Q6: Can you prove impact beyond "technically possible"?

  • XSS -> show actual session theft or action execution, not just alert(1)
  • SSRF -> confirm OOB callback (DNS/HTTP), not just URL echo in error message
  • SQLi -> show actual data extracted from a real table
  • IDOR -> show actual other-user data in response body, not just 200 status

Q7: Not on the Never-Promote list?

Never promote to Completed without a chain:

Self-XSS only (no CSRF trigger)
Open redirect alone (no OAuth/ATO chain)
CORS wildcard without credentialed exfil PoC
SSRF DNS-only (no internal service access)
Rate limit without demonstrated impact
Version banner alone
Missing headers alone (no impact PoC)

Pre-Severity Gate (run before labelling CRITICAL or HIGH)

  1. Have you validated the FULL chain to attacker-attainable impact, or only one primitive?
  2. What does the attacker walk away with in one concrete sentence?
  3. Have you reproduced the full chain end-to-end at least twice?
  4. Is there a validation step (signature check, audience check, MFA) still gating the chain?

A "primitive confirmed" != exploitable. Downgrade until the gate is bypassed.

Decision

ResultAction
All 7 YES + Pre-Severity Gate cleanMove FIND to Vulns/Completed/. Update status in Vuln-index.md. Run python3 scripts/find-lint.py and fix any gaps (Description/PoC/Impact/Remediation + CVSS for HIGH/CRITICAL) so it is report-ready. Then run /evidence.
Any NOKeep in Vulns/Research/. Update status to PARTIAL (reason) in Vuln-index.md. Document what is missing.
Q7 chain requiredMove to Vulns/Research/ with note "chain required: [what is needed]".

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

arsenal

무료

Wiki-first "what do I use" lookup - pick the automated TOOL (wiki/tools/), then the PAYLOAD/technique (wiki/payloads/ + wiki/cheatsheets/), for a surface/service/vuln-class BEFORE hand-rolling or working from memory. Use for "tool for <service>", "automated tools for web/<service>", "what should I run on <surface>", "which tool for <X>", "payloads for <X>", "payload arsenal", "cheatsheet for <X>", "how do I exploit <tech/class>", "exploit/attack chain for <X>", "arsenal", any SSRF/XSS/SQLi/SSTI/LFI/JWT/XXE/IDOR/NoSQL/deserialization/CSRF/CORS/CRLF/GraphQL/smuggling/web-cache/OAuth/SAML/MFA/crypto/LDAP/XPath/WebAuthn/file-upload/IMDS/prompt-injection/Modbus ask, plus "privesc arsenal", "CVE arsenal", "default creds", "nuclei templates", "sqlmap/hydra/nmap/bloodhound", "password attacks".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH3332026년 9월 1일 업데이트

bb-workflow

무료

Autonomous bug-bounty campaign driver. Runs a full programme end to end with no operator approvals - the deterministic driver (scripts/campaign.py) owns pass state, generates the killchain board from recon, and prints the exact next action (including which Skill and tool to run) every turn. Use when starting or resuming a bug-bounty engagement, "run the bb workflow", "hunt this program", "9-pass campaign", or when handed a *.scope wildcard to test for TIER1 findings. Single agent, refuter-verified, wiki-first, tool-first.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH3332026년 9월 1일 업데이트

campaign-health

무료

Health check for the bb/pt/ctf workflow driver subsystem - verifies everything is in place so every machine runs the same. Checks vault-content consistency (scripts present, JSON valid, routing wired, all 69 tool pages carry phase:, the tool index resolves, the hook edits are in place) AND per-machine wiring (the three workflow skills symlinked, hooks registered, imports work), then runs a live init->board->next smoke test. Use when setting up the workflow on a new machine, after a vault sync, when the driver misbehaves, or on "bb-health", "campaign health", "is the workflow set up", "check hooks and scripts", "why is the board not working".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH3332026년 9월 1일 업데이트

chrome-devtools-browser

무료

Bring up a REAL, visible, interactive chromium on the Kali VM that the operator logs into (Smart-ID / Mobile-ID / any manual auth or MFA/CAPTCHA), while the agent drives and observes it live through the chrome-devtools MCP (navigate, DOM snapshot, network capture, screenshots, console, evaluate). Use whenever a target needs a MANUAL login the agent cannot complete headlessly, when you need to capture an authenticated session / the real API calls a page makes, or to confirm/screenshot a DOM-XSS. Triggers - "open a browser", "log in manually", "smart-id / mobile-id / national id login", "mfa / 2fa login", "solve the captcha", "drive the browser", "capture the authenticated session / network".

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH3332026년 9월 1일 업데이트

claude-md-improver

무료

OFFLINE FALLBACK for the claude-md-management plugin - prefer that plugin when it is installed. Audit and improve CLAUDE.md files - scan for CLAUDE.md files, evaluate quality against templates, output a report, then make targeted updates. Invoke explicitly (/claude-md-improver) when the plugin is unavailable.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH3332026년 9월 1일 업데이트

coverage

무료

Show per-asset vuln-class coverage gaps for the active engagement so nothing in scope is skipped. Use when asked "coverage", "what haven't we tested", "test gaps", "are we thorough", or before calling an engagement done.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Encod3d-Sec/TORCH3332026년 9월 1일 업데이트

Encod3d-Sec의 스킬 모두 보기

이 스킬의 문제 신고