Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/transilienceai/communitytools/techstack-identificationnpx skills add transilienceai/communitytools --skill techstack-identificationgit clone --depth 1 https://github.com/transilienceai/communitytoolsWhat it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00045 | $0.00830 |
| Opus 5 | $0.00023 | $0.00415 |
| Sonnet 5 | $0.00009 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
techstack-identification scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- backend/reference/patterns.md 5.0 KB
- backend/SKILL.md 1.5 KB
- correlation/reference/patterns.md 6.4 KB
- correlation/SKILL.md 1.8 KB
- frontend/reference/patterns.md 5.4 KB
- frontend/SKILL.md 1.5 KB
- infra/reference/patterns.md 8.1 KB
- infra/SKILL.md 1.8 KB
- osint/reference/patterns.md 5.6 KB
- osint/SKILL.md 1.8 KB
- security/reference/patterns.md 5.0 KB
- security/SKILL.md 1.8 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 69 lines · 45 tokens per session scan A 997684d33913
techstack-identification is a skill published in the GitHub repository transilienceai/communitytools (498 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 830 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
pentester-playwright
Phases 1b/3/4 authorized browser automation — SPA recon, multi-role auth, route/API catalog, PoC screenshots, Evidence landing (scoped proxy). Skill-gate read for web phases. Use when Phase 1b/3/4 web work, JS-rendered SPA, real browser needed, HAR/network capture, or Playwright PoC evidence.
osint-recon
Phase 1 conditional OSINT depth — four-dimension model (server→site→domain→people; people is conditional). Skill-gate companion to pentester-enum-services / pentester-recon. Use for passive OSINT depth, full recon dimensions, author tracking, not as Phase 0/Schema replacement.
pentester-exploit
Phase 4 exploitation — PoC construction, exploit-db/msf search, safe verification. Required Skill-gate read at Phase 4. Use when starting Phase 4, exploitation, exploit, PoC, exploit-db, msf, Metasploit, or payload delivery.
pentester-recon
Phase 1 intelligence recon methodology — passive+active recon, stack fingerprint, attack-surface map. Required Skill-gate read at Phase 1 (with pentester-enum-services). Use when starting Phase 1, intelligence gathering, recon, reconnaissance, OSINT prep, target profiling, or attack surface mapping.
pentester-toolkit
Provision the pinned pentest toolset via DotSlash for the current scanenv (host-kali or kali-target-${ID}). Adapter, not a tool wrapper.
pentester-waf-bypass
Phase 4 conditional — WAF/filter bypass for authorized CTF/range/pentest when payloads are blocked. Use at Phase 4 if blocked, or when user mentions WAF bypass, filter evasion, SQL/XSS/command-injection bypass, or security filter analysis.