Techstack Identification logo

Techstack Identification

Organization
transilienceai
techstack-identification

OSINT-based technology stack identification. Routes to 6 domain sub-skills (frontend, backend, infra, security, osint, correlation) to discover a target's stack from publicly available signals.

Overview

Publishertransilienceai
Repositorycommunitytools
Skill nametechstack-identification
Stars
565
Forks
81
Bundled files
6
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 6 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by transilienceai on GitHub. Read the source before you install it.

Installation

Install the Techstack Identification AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/transilienceai/communitytools/tree/main/skills/techstack-identification
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/transilienceai/communitytools.git /tmp/communitytools
mkdir -p .claude/skills
cp -r /tmp/communitytools/skills/techstack-identification .claude/skills/techstack-identification
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Techstack Identification in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Techstack Identification on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Techstack Identification is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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-skillIdentifiesRead
frontendJS frameworks, meta-frameworks, CSS libraries, build tools, CMS via DOM/HTML/JSfrontend/SKILL.md
backendWeb servers, runtimes, languages, frameworks, DB, APIs, CMSbackend/SKILL.md
infraCloud, CDN/WAF, DNS, TLS/CT, DevOps, asset discovery (domains/subdomains/IPs)infra/SKILL.md
securitySecurity headers, CSP, email auth, security.txt, third-party SaaSsecurity/SKILL.md
osintPublic repos (GitHub/GitLab), job postings/ATS, Wayback Machineosint/SKILL.md
correlationCross-validation, confidence scoring, conflict resolutioncorrelation/SKILL.md

Routing by Objective

ObjectiveMount
Full stack discoveryinfra → (frontend, backend, security, osint) → correlation
CDN/WAF identification onlyinfra
API surface mappingbackend
Supply-chain / SaaS exposuresecurity + osint
CVE matching by versionbackend + frontend (then correlation)
Migration / historical contextosint (web archive) + correlation
CMS fingerprintfrontend (HTML generators) + backend (CMS paths/cookies)
Asset inventory onlyinfra (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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Techstack Identification AI skill do?

OSINT-based technology stack identification. Routes to 6 domain sub-skills (frontend, backend, infra, security, osint, correlation) to discover a target's stack from publicly available signals.

Why use Techstack Identification on TypingMind?

Because you install it once and use it with any model. Techstack Identification is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Techstack Identification in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/transilienceai/communitytools/tree/main/skills/techstack-identification. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Techstack Identification?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Techstack Identification?

As many as you like. As long as a model supports skills, you can use Techstack Identification with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Techstack Identification AI skill free?

Yes. It is published on GitHub by transilienceai under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇