Skip to content
cccskills
FreePublished on GitHub

techstack-osint

OSINT-side tech-stack identification — public repositories (GitHub/GitLab), job postings & ATS, and Wayback Machine historical snapshots.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595 stars(GitHub 595 + cccskills 0)
Works withGitHubGitLab

Run score Not tested

See how to install

Files included (2)

  • SKILL.md1.8 KB
  • reference/patterns.md5.6 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

OSINT Tech-Stack Identification

Scope

Recover technology signals from public, non-target sources:

  • Code repositories — public GitHub/GitLab orgs, language stats, dependency files (package.json, requirements.txt, Gemfile, go.mod, pom.xml, composer.json), CI configs, Dockerfiles.
  • Career signals — career page, ATS platform (Greenhouse, Lever, Workday, Ashby, iCIMS, Taleo, etc.), job-description tech requirements.
  • Web archives — Wayback Machine CDX queries to detect historical stack and migrations.

These provide indirect but valuable corroboration; weight lower than direct technical signals.

Signals (input)

  • Public repos: org metadata, language map, dependency files, CI/CD configs, Dockerfile FROM lines
  • Career page URL + ATS URL pattern + job-description text
  • Wayback CDX snapshots (every 6-12 months over 5y)

Inferences (output)

  • Languages and frameworks (with version ranges from dep files)
  • CI/CD platform and pipeline maturity
  • Container base images and orchestration manifests
  • ATS-derived hiring profile (startup vs enterprise)
  • Tech-mention frequency (Core Stack ≥50% / Common 25-50% / Occasional <25%)
  • Historical stack timeline + migration events (jQuery → React, WordPress → Next.js, on-prem → cloud)

Techniques

See reference/patterns.md.

When to use

  • Phase 2 of tech-stack OSINT (corroborating signal layer)
  • Validating a hypothesis from direct signals (e.g. confirm Node.js via package.json)
  • Detecting recent migrations (current stack different from historical)
  • Inferring internal stack when public surface is heavily obscured (Cloudflare-fronted, headless API, etc.)

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Offensive AI security testing and exploitation framework. Systematically tests LLM applications for OWASP Top 10 vulnerabilities including prompt injection, model extraction, data poisoning, and supply chain attacks. Integrates with pentest workflows to discover and exploit AI-specific threats.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

API security testing - GraphQL, REST API, WebSocket, and Web-LLM attack techniques.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Stitches confirmed single-asset findings into multi-hop attack paths across the organization. Builds a graph where nodes are assets and edges are confirmed exploit hops citing the findings that enable them.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Acquire an authenticated session THROUGH MFA/OTP on an in-scope target and emit a reusable session artifact (Playwright storageState + Bearer) so executors can test the post-auth attack surface. Use when the highest-value authenticated classes (BOLA/IDOR/mass-assignment/injection on the real data APIs) are blocked because login is gated by SMS-OTP or TOTP MFA. Distinct from the authentication skill (which ATTACKS auth); this one legitimately authenticates and hands the session to the rest of the engagement.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Authentication security testing - auth bypass, JWT attacks, OAuth flaws, password attacks, 2FA bypass, CAPTCHA bypass, and bot detection evasion.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

Smart contract security testing and blockchain CTF exploitation. Covers Solidity vulnerability analysis, EVM storage manipulation, delegatecall attacks, CREATE/CREATE2 address prediction, and common DeFi exploit patterns. Use when analyzing Solidity contracts, solving blockchain challenges, or testing smart contract security.

The English summary is being prepared. Showing the original description.

transilienceai/communitytools595Updated Jul 30, 2026

See all skills by transilienceai

Report a problem with this skill