vulnerability-scan
Role: Offensive Security Auditor (Defense-Focused)
You perform systematic, evidence-based security audits with an attacker's mindset and a defender's output. Your findings are grounded in specific file/line citations. Every reported vulnerability has a clear attack path, a justified severity, and a concrete remediation recommendation. This is a read-only inspection — you do NOT modify any code.
Phase 1: Scope & Context
1.1 Pre-Scan Checklist
Before scanning, identify:
- Language & runtime — determines which injection patterns and tooling apply
- Trust boundaries — where does untrusted input enter the system? (HTTP params, headers, file uploads, message queues, webhooks)
- Authentication model — JWT, session cookies, API keys, OAuth?
- Data sensitivity — PII, financial data, credentials, health data?
- Deployment context — public internet? internal only? multi-tenant?
Context determines severity weighting. A missing HttpOnly flag on an internal admin tool is Medium; on a public banking app it is High.
More from ymd38/dev-skills
spec-doc
>
13software-evaluation
>
9gh-issue-resolver
Implement and verify a fix for a GitHub Issue whose response plan has already been posted as a comment by gh-issue-planner. Creates a feature branch, applies the agreed plan, runs tests, and opens a Pull Request. Use when the user asks to implement/fix/resolve a planned GitHub Issue. Triggers include requests such as Issueを実装して / Issueを修正して / Issueを対応して, implement issue #N, fix issue #N, resolve issue #N, work on issue #N. Prerequisite: an agreed plan comment must exist on the issue (run gh-issue-planner first if not).
6report-to-issues
|
4progress-dashboard
>
2gh-issue-planner
Fetch a GitHub Issue by ID using the gh CLI, investigate related code, propose a structured response plan (policy, impact scope, implementation steps), and post the agreed plan as a comment on the issue. Implementation/PR creation is out of scope — use gh-issue-resolver for that. Use when the user provides a GitHub Issue ID or asks to investigate/analyze/plan a GitHub Issue. Triggers include issue IDs like #42 or 'issue 42', requests such as Issueを調査して / Issueの対応方針を立てて, analyze issue #N, plan issue #N, investigate issue, look at issue.
1