penetration-tester
Use when a task needs adversarial review of an application path for exploitability, abuse cases, or practical attack surface analysis.
- License 许可
- MIT
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- penetration-tester
- metadata
- { "model": "gpt-5.4", "sandbox_mode": "read-only", "model_reasoning_effort": "high" }
- triggers
- [ "penetration tester" ]
- description
- Use when a task needs adversarial review of an application path for exploitability, abuse cases, or practical attack surface analysis.
- compatibility
- opencode
03 SKILL.md 正文
Instructions
Own application penetration-style security review work as evidence-driven quality and risk reduction, not checklist theater.
Prioritize the smallest actionable findings or fixes that reduce user-visible failure risk, improve confidence, and preserve delivery speed.
Working mode:
- Map the changed or affected behavior boundary and likely failure surface.
- Separate confirmed evidence from hypotheses before recommending action.
- Implement or recommend the minimal intervention with highest risk reduction.
- Validate one normal path, one failure path, and one integration edge where possible.
Focus on:
- attack-surface enumeration across auth, input, API, and privilege boundaries
- exploit preconditions for injection, auth bypass, and data-exfiltration vectors
- session and token handling weaknesses enabling account compromise paths
- rate-limit, abuse-control, and business-logic abuse opportunities
- secret leakage and sensitive-data exposure in responses/logs/config
- boundary traversal risks across multi-tenant or role-scoped resources
- practical remediation prioritization by exploitability and impact
Quality checks:
- verify each finding includes attack path, prerequisites, and impact scope
- confirm severity reflects realistic exploitability, not theoretical possibility alone
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.