Javascript Surface Analyzer

Enumerate and analyze client-side JavaScript for hidden endpoints, secrets, dangerous sinks, and exploitable browser behaviors.

10 stars 6 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add 1ikeadragon/awesome-offsec-claude --skill javascript-surface-analyzer
Manual install
git clone --depth 1 https://github.com/1ikeadragon/awesome-offsec-claude.git /tmp/awesome-offsec-claude
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-offsec-claude/javascript-surface-analyzer ~/.claude/skills/javascript-surface-analyzer

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# JavaScript Surface Analyzer

## Purpose
Extract attacker-relevant intelligence from front-end code and convert it into testable hypotheses.

## Inputs
- `target_url`
- `seed_pages` (optional)
- `auth_context` (optional)

## Workflow
### Phase 1: Asset Enumeration
1. Collect static and dynamic script URLs.
2. Expand via source maps and chunk manifests where available.
3. Track script origin, load condition, and execution context.

### Phase 2: Artifact Extraction
1. Endpoints, route builders, and API clients.
2. Header/token construction logic.
3. Feature flags, debug modes, hidden route toggles.
4. Secret candidates and key material references.

### Phase 3: Sink Analysis
1. DOM write sinks: `innerHTML`, `outerHTML`, template insertion.
2. Code execution sinks: `eval`, `Function`, `setTimeout` string usage.
3. URL/navigation sinks: dynamic redirects, iframe/src assignments.
4. Storage sinks: local/session storage of sensitive artifacts.

### Phase 4: Controllability Assessment
1. Determine if attacker can influence source data.
2. Trace sanitization or encoding at boundaries.
3. Estimate exploit preconditions per sink.

### Phase 5: Follow-up Planning
1. Create endpoint verification cases.
2. Create DOM-XSS and open redirect probes.
3. Create token misuse and privilege abuse checks.

## Minimum Extraction Targets
| Category | Required Extraction |
|---|---|
| API surface | method + path hints + caller context |
| Secrets | key/token candidates with confidence tag |
Read the full skill on GitHub

Details

Skill name
javascript-surface-analyzer
Path
javascript-surface-analyzer/SKILL.md
Repo updated
19 March 2026

FAQ

What does the Javascript Surface Analyzer skill do?

Enumerate and analyze client-side JavaScript for hidden endpoints, secrets, dangerous sinks, and exploitable browser behaviors.

How do I install the Javascript Surface Analyzer skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add 1ikeadragon/awesome-offsec-claude --skill javascript-surface-analyzer. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Javascript Surface Analyzer popular?

It lives in 1ikeadragon/awesome-offsec-claude, which has 10 GitHub stars and 6 forks.

Related skills

Advanced Reconnaissance

10

1ikeadragon/awesome-offsec-claude

Elite methodology for discovering maximum attack surface with minimal detection (5-Layer Approach).

Other

AI LLM Attacks

10

1ikeadragon/awesome-offsec-claude

Elite AI/LLM exploitation specialist - prompt injection, jailbreaking, agent exploitation, RAG poisoning, multi-modal attacks, model extraction, and system prompt leakage for CTF and red team engagements

AI, LLMs & Agents

API Attack Surface Mapper

10

1ikeadragon/awesome-offsec-claude

Build a full API inventory, trust-boundary map, and prioritized test matrix from specification and observed behavior.

Software Development

Procedural Grounded Theory

5

maydengximin-sketch/procedural-grounded-theory-skill

程序化扎根理论(Procedural / Straussian Grounded Theory, Strauss & Corbin)专项方法学助手,聚焦"用一套系统化的编码程序与工具,从质性资料中建构出一个结构清晰的解释性理论"的完整链路——不是泛扎根,也不是经典 Glaser / 建构主义 Charmaz,而是专攻 Strauss & Corbin / Corbin & Strauss 一脉的程序化取向。当用户要做程序化扎根理论的任何环节时使用:判断"我该用程序化扎根,还是经典 Glaser / 建构主义 Charmaz / 主题分析 / 现象学"、写清程序化扎根的认识论立场(后实证到实用主义、符号互动论根基、Strauss 与 Glaser 因"涌现 vs 强加 emergence vs forcing"分道、1990/1998/2008/2015 版本演变)、研究问题与理论敏感性(theoretical sensitivity)与文献的位置(程序化允许文献作为敏感性来源)、开放编码(概念化、贴标签→概念→范畴、属性与维度 properties & dimensions、逐行微观分析、提问与比较)、主轴编码(编码范式 coding paradigm:因果条件—现象—脉络—中介条件—行动/互动策略—结果,把范畴与子范畴按范式重连而非归类)、选择性编码(核心范畴判定标准、故事线 s

Software Development

Code Review Verifier

10

1ikeadragon/awesome-offsec-claude

Independently validate code-review findings with alternate methodology, severity calibration, and blind-spot discovery.

Software Development

Oldhand Build

9

berwinsingh/oldhand

Implements a planned change the lazy, correct way: reuse what the codebase has, then the standard library, the platform and installed dependencies, and only then the least new code, fixing the whole class of bug at the shared point. Takes a baseline of the repo checks before the first edit, leaves one focused regression check, proves that check guards the fix with a mutation run (mutate.py), and compares the checks with the baseline. Records unit, integration and mutation results in the Oldhand ledger and writes build.md in the task's .oldhand folder. Use when the user says "implement the plan

Software Development

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.