사용 방법
- 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
- 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
- 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/transilienceai/communitytools --skill techstack-identification시작 전 확인
- 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
- 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서
원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.
Tech Stack Identification
Passive OSINT reconnaissance to identify a target's technology stack. No credentials, no active scanning — only publicly available signals.
Quick Start
1. Provide company name (+ optional domain hint)
2. Run infra first (asset inventory) → frontend / backend / security / osint in parallel
3. Pass all signals into correlation → final report (JSON + Markdown)Domain Sub-Skills
| Sub-skill | Identifies | Read |
|---|---|---|
| frontend | JS frameworks, meta-frameworks, CSS libraries, build tools, CMS via DOM/HTML/JS | frontend/SKILL.md |
| backend | Web servers, runtimes, languages, frameworks, DB, APIs, CMS | backend/SKILL.md |
| infra | Cloud, CDN/WAF, DNS, TLS/CT, DevOps, asset discovery (domains/subdomains/IPs) | infra/SKILL.md |
| security | Security headers, CSP, email auth, security.txt, third-party SaaS | security/SKILL.md |
| osint | Public repos (GitHub/GitLab), job postings/ATS, Wayback Machine | osint/SKILL.md |
| correlation | Cross-validation, confidence scoring, conflict resolution | correlation/SKILL.md |
Routing by Objective
| Objective | Mount |
|---|---|
| Full stack discovery | infra → (frontend, backend, security, osint) → correlation |
| CDN/WAF identification only | infra |
| API surface mapping | backend |
| Supply-chain / SaaS exposure | security + osint |
| CVE matching by version | backend + frontend (then correlation) |
| Migration / historical context | osint (web archive) + correlation |
| CMS fingerprint | frontend (HTML generators) + backend (CMS paths/cookies) |
| Asset inventory only | infra (domain discovery, subdomain enum, IP attribution, CT) |
Confidence Levels
- High: 3+ independent sources OR explicit identifier (header/meta/global) + supporting evidence + version known
- Medium: Single strong source OR multiple indirect signals (URL patterns, cookies, DOM attrs, job postings)
- Low: Speculative — single weak signal, conflicting data, or archive-only evidence
Computed in correlation/. Target distribution: 50-70% High, 20-35% Medium, <15% Low.
Final Report Schema
json
{ "report_id": "uuid", "company": "string", "primary_domain": "string",
"discovered_assets": {"domains", "subdomains", "ip_addresses", "certificates", "api_portals"},
"technologies": {
"frontend": [{"name", "version?", "confidence", "evidence": []}],
"backend": [...], "infrastructure": [...], "security": [...],
"devops": [...], "third_party": [...] },
"confidence_summary": {"high_confidence", "medium_confidence", "low_confidence", "overall_score"} }Rate Limits
crt.sh 10/min · GitHub (unauth) 60/h · HTTP 30/min/domain · DNS 30/min · Wayback CDX 15/min · WHOIS 5/min.
Ethics
Passive only. No active scanning, credentialed access, zone transfers, or brute force. Public sources only. Log every external request for audit.
