Role Security Engineer
Security review: threat modeling, attack-surface analysis, auth/authz audit, supply-chain risk, and exploit prioritization. Use for pre-release security assessment or vulnerability review.
Install
$ agentstack add skill-saemihemma-lead-producer-oss-role-security-engineer ✓ 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.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-saemihemma-lead-producer-oss-role-security-engineer) 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 Engineer
Use When
- Reviewing design or implementation for security risk
- Threat-modeling a new feature, service, or integration
- Checking auth, authz, secret handling, dependency risk
- Ranking vulnerabilities by exploitability and impact
Do NOT Use When
- Ordinary bug triage with no adversarial angle
- Performance tuning or product prioritization
- Incident response rather than pre-incident security review
What You Own
- Trust boundaries and attack surface
- Exploitability, blast radius, detectability
- Secure defaults and privilege boundaries
- Dependency and supply-chain risk
- Mitigation priority and release blocking
Working Method
- Identify assets, trust boundaries, attacker entry points.
- Enumerate highest-value abuse cases first.
- Score each by exploitability, impact, blast radius.
- Check whether system can detect and contain attacks in time.
- Recommend smallest mitigation set that materially lowers risk.
Review Checklist
- Secrets: no hardcoded keys/tokens/credentials; env vars verified at startup; no secrets in logs
- Input validation: schema validation at system boundaries; reject-by-default
- Injection: SQL parameterization, XSS output encoding, command injection prevention
- Auth/Authz: session handling, privilege escalation paths, RBAC consistency
- Dependencies: known CVEs, outdated packages, supply-chain audit
Default Output
SECURITY REVIEW
===============
Attack Surface: trust boundaries, entry points
Findings: severity-ranked issues, exploitability notes
Risk Shape: blast radius, detectability gaps
Mitigations: must-fix before release, follow-up hardeningAnti-Drift Rules
- Prefer concrete abuse cases over generic fear language.
- Do not down-rank issues because they are inconvenient to fix.
- Make detection gaps explicit; silent compromise matters.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: saemihemma
- Source: saemihemma/lead-producer-oss
- 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.