Skill
ai-threat-testing
Offensive AI security testing and exploitation framework. Systematically tests LLM…
@transilienceaiView SkillSecurity
Skill
/backend
Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.
Install
$ npx -y skills add transilienceai/communitytools --skill backend --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/backend
Context preview
The summary Claude sees to decide when to auto-load this skill.
Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.
SKILL.md
backend.SKILL.mdname: techstack-backend
description: Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.
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.txt` directives
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
See [reference/patterns.md](reference/patterns.md).
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
Read more
name: techstack-backend description: Backend tech-stack identification — web servers, runtimes, languages, frameworks, databases, APIs, and CMS via HTTP headers, cookies, error pages, and API discovery.
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.txt` directives
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
See [reference/patterns.md](reference/patterns.md).
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
Ships withcommunitytools
Open-source Claude Code skills and agents for AI-powered penetration testing, bug bounty hunting, AI threat testing, and security reconnaissance — from the team at Transilience.ai
Get the whole plugin
Stats
575
Stars
84
Forks
Maintained
Maintenance
Python
Language
MIT
License
2mo ago
Last commit
10mo ago
Created
4h ago
Added
Repo: transilienceai/communitytools
Other skills on communitytools.
@transilienceaiView SkillSkill
api-security
API security testing - GraphQL, REST API, WebSocket, and Web-LLM attack techniques.
@transilienceaiView SkillSkill
attack-path-stitcher
Stitches confirmed single-asset findings into multi-hop attack paths across the organization.…
@transilienceaiView SkillSkill
authenticated-session-…
Acquire an authenticated session THROUGH MFA/OTP on an in-scope target and emit a reusable…
@transilienceaiView SkillSkill
authentication
Authentication security testing - auth bypass, JWT attacks, OAuth flaws, password attacks,…
@transilienceaiView SkillSkill
blockchain-security
Smart contract security testing and blockchain CTF exploitation. Covers Solidity…
@transilienceaiView Skill