Backend
Skill LeoWSY-hashblue/-communitytools-custom/skills/techstack-identification/backend
Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.From its SKILL.md
No install line here. The name this skill would be installed by is not one plain word to a shell. It starts with -, or carries a space, a character such as &, # or $ that the shell acts on, or punctuation beyond . _ - : +, such as a fullwidth bracket some tools turn into a real one. A line built from it might not run as the install it claims to be, so there is none.
The repository will have the real instructions: github.com/LeoWSY-hashblue/-communitytools-custom
One thing to look at
- 3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Backend Tech-Stack Identification
Scope
Identify server-side technologies: web servers (nginx, Apache, IIS), runtimes (Node, Python, PHP, Ruby, Java, .NET), backend frameworks (Express, Django, Flask, Rails, Laravel, Spring, ASP.NET), databases (Postgres, MySQL, Mongo, Redis), CMS (WordPress, Drupal, Magento), and API surfaces (REST, GraphQL, OpenAPI).
Signals (input)
- HTTP response headers —
Server,X-Powered-By,X-AspNet-Version,X-Drupal-*,X-Generator, etc. - Cookies — session-name fingerprints (
PHPSESSID,JSESSIONID,_rails_session, ...) - Error page bodies (404, 500)
- Path patterns hinting CMS (
/wp-admin/,/sites/default/) - API subdomains and OpenAPI/Swagger/GraphQL endpoints
robots.txtdirectives
Inferences (output)
- Web server + version
- Runtime / language + version
- Backend framework (with implied runtime)
- CMS + version
- Database (often indirect — via ORM dependency or hosted-DB DNS)
- API style (REST/GraphQL/gRPC) and authentication scheme
Techniques
When to use
- Phase 2/3 of a tech-stack OSINT engagement
- Mapping server-side attack surface (RCE, SSRF, deserialization)
- CVE matching by server + version
- Locating GraphQL / OpenAPI for follow-on api-security testing