Install
$ agentstack add skill-codexstar69-bug-hunter-security-review ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Security Review
This is a bundled local Bug Hunter companion skill. It packages a security-focused review workflow without introducing any external marketplace dependency.
Purpose
Use this skill for deeper security audits than a simple bug hunt, especially when the user wants:
- a full security review
- PR security validation
- weekly security scanning
- dependency reachability + code review together
- threat-model-driven analysis
Workflow
- Ensure
.bug-hunter/threat-model.mdexists.
- If missing, invoke the bundled
threat-model-generationskill.
- Determine the scan mode from the request:
- PR → diff-scoped review via
commit-security-scan - staged → staged-only security review
- weekly → recent commit range on the default branch
- full → full repository security audit
- If dependency scanning is relevant, run:
node scripts/dep-scan.cjs --target --output .bug-hunter/dep-findings.json
- Scan code for STRIDE threats using Bug Hunter-native conventions.
Reuse:
.bug-hunter/triage.json.bug-hunter/threat-model.md.bug-hunter/security-config.json.bug-hunter/dep-findings.json
- Validate severe findings using the bundled
vulnerability-validationskill.
- Produce structured outputs compatible with the Bug Hunter pipeline.
Outputs
Primary artifacts should stay inside .bug-hunter/:
.bug-hunter/findings.json.bug-hunter/referee.json.bug-hunter/report.md.bug-hunter/dep-findings.jsonwhen dependency review is enabled.bug-hunter/fix-strategy.jsonif the user wants remediation planning
Important constraints
- Keep all paths Bug Hunter-native; do not emit
.factory/*artifacts. - Prefer validated, exploitability-aware findings over raw volume.
- For patching requests, hand findings back to the normal Bug Hunter fix pipeline rather than inventing a second patch system.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: codexstar69
- Source: codexstar69/bug-hunter
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.