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/securitytalent/bugskill-ai/jsanalyzernpx skills add SecurityTalent/bugskill-ai --skill jsanalyzergit clone --depth 1 https://github.com/SecurityTalent/bugskill-aiWhat 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.00075 | $0.01360 |
| Opus 5 | $0.00037 | $0.00680 |
| Sonnet 5 | $0.00015 | $0.00272 |
| Haiku 4.5 | $0.00007 | $0.00136 |
Grade B, and why
JsAnalyzer scanned grade B with 1 finding 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 2d 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.
Harvests environment variablesmediumData exfiltration
Enumerating or grepping the environment for keys collects credentials unrelated to what the mod says it does.
# Extract secrets Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JsAnalyzer
Orchestrator-based JS security analysis. Primary context delegates all heavy work to specialized agents.
Architecture: Orchestrator Pattern
PRIMARY CONTEXT (Light Orchestrator)
│
├── Phase 1-3: Spawn in PARALLEL
│ ├── js-grep-analyzer (haiku) → paths, endpoints
│ ├── js-tool-runner (haiku) → doctorswzl output
│ └── js-architecture-analyzer (opus) → architecture docs
│
├── Phase 4: Spawn in PARALLEL
│ ├── source-sink-tracer (opus) × N
│ ├── postmessage-analyzer (opus) × N
│ ├── api-investigator (opus) × N
│ └── secrets-analyzer (opus) × 1
│
└── Phase 5: Synthesize (light)
Primary context NEVER:
- Runs greps directly
- Parses JSON output
- Reads large files for analysis
Primary context ONLY:
- Spawns agents
- Waits for results (TaskOutput)
- Creates final summary reports
Workflow Routing
| Trigger | Workflow | Action |
|---|---|---|
/js-analyze <domain> or /jsa <domain> |
LiveSite.md | Acquire from live site → FullScan |
/js-analyze (in folder with .js files) |
FullScan.md | All 5 phases with agents |
| "analyze js files" | Analyze.md | Phases 1-3 only |
| "review findings" | Review.md | Phases 4-5 only |
Note: If given a domain/URL, use LiveSite workflow. If in a folder with JS files, use FullScan.
Execution
When triggered, IMMEDIATELY:
- Read workflow:
${PAI_DIR}/skills/JsAnalyzer/workflows/FullScan.md - Execute the orchestrator pattern as specified
- Spawn agents in parallel where indicated
- Wait for agents with TaskOutput
- Create summary reports
Agents Used
| Agent | Model | Purpose |
|---|---|---|
js-grep-analyzer |
haiku | Fast grep extraction |
js-tool-runner |
haiku | Tool execution |
js-architecture-analyzer |
opus | Deep architecture analysis |
source-sink-tracer |
opus | Flow tracing |
postmessage-analyzer |
opus | postMessage security |
api-investigator |
opus | API endpoint analysis |
secrets-analyzer |
opus | Credential assessment |
What ships with it
22 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.
- bun.lock 2.9 KB
- EXTRACTION.md 6.2 KB
- INSTALL.md 4.7 KB
- package.json 849 B
- scripts/extract-inline-batch.sh 1.9 KB runs code
- scripts/extract-inline-js.sh 3.8 KB runs code
- src/configs/agents.ts 2.7 KB runs code
- src/configs/grep-patterns.ts 5.5 KB runs code
- src/configs/outputs.ts 4.2 KB runs code
- src/configs/workflows.ts 4.8 KB runs code
- src/index.ts 4.1 KB runs code
- src/orchestrators/analyze.ts 5.8 KB runs code
- src/orchestrators/fullscan.ts 5.7 KB runs code
- src/orchestrators/review.ts 9.7 KB runs code
- src/README.md 4.3 KB
- src/types/index.ts 1.4 KB runs code
- tsconfig.json 471 B
- VERIFY.md 7.2 KB
- workflows/Analyze.md 8.1 KB
- workflows/FullScan.md 9.2 KB
- workflows/LiveSite.md 6.7 KB
- workflows/Review.md 20 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.
- 2d ago First seen · 184 lines · 75 tokens per session scan B 337450922a10
JsAnalyzer is a skill published in the GitHub repository SecurityTalent/bugskill-ai (5 stars, last pushed 17d ago), licensed MIT. It adds 75 tokens to every session and 1,360 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (harvests environment variables). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
srt-whiteboard-animation
将 SRT 字幕做成暖米黄纸张底的白板手绘动画：读字幕→输出配图策略→确认后生成统一风格线稿→按叙事语义标注分区→预览台调整→渲染 MP4。编排沿用分区遮罩揭示（annotation.json / sequence / startMs / protectedRegions），但每个区域内的落墨换成 stream 的连续笔迹（骨架/网格 ink→color）。当用户提供 SRT 字幕并要求"字幕做成白板手绘/流式笔迹视频""SRT 生成白板动画""按字幕分镜画手绘"时触发。.
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
seo
Deterministic LLM-first SEO audits for websites, blog posts, and GitHub repositories. Use this when the user asks to "perform SEO analysis", "run SEO audit", "analyze SEO", "check technical SEO", "review schema", "Core Web Vitals", "E-E-A-T", "hreflang", "GEO", "AEO", or GitHub repository SEO optimization. For…
playwright-best-practices
Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions…
open-map-stack
Use textual agent instructions for GIS and geospatial work: source discovery and provenance, vector/raster/point-cloud pipelines, CRS and metric analysis, spatial SQL, routing and isochrones, QGIS projects, tile generation, and web maps. Use advanced tools and formats such as OSM, Overture, STAC, Sentinel/Landsat…
globalpercent
GlobalPercent — build a global-macro-probability panel for an investment research system. Merges public probability data from prediction markets (Polymarket + Kalshi), classifies every market into macro modules (monetary policy / macro economy / AI / etc.), and shows the whole market's expected-probability state at a…