Security review
Small, harness-neutral engineering skills for coding agents
npx -y skills add kevinb361/agent-skills --skill security-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
3 things to look at
- 13 days oldThe repository was created 13 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Review a change or subsystem using an explicit threat model. Use for authentication, authorization, untrusted input, secrets, external services, filesystem access, deployment, or other security-sensitive surfaces.
SKILL.md
1.3 KB, as published. Nobody here has run it
Security review
Remain read-only unless the user separately asks for remediation.
Threat model
Identify:
- protected assets
- trust boundaries and actors
- attacker-controlled inputs
- privileged operations
- persistence and audit surfaces
- availability dependencies
Then examine relevant code and configuration for spoofing, tampering, repudiation gaps, information disclosure, denial of service, and privilege escalation. Also check default behavior, error handling, secret lifecycle, dependency trust, and fail-open paths.
Do not produce generic checklist findings. Every reported issue needs a plausible exploit or failure path grounded in the implementation.
Output
For each finding provide:
- severity: critical, high, medium, or low
path:line- affected asset and trust boundary
- exploit scenario and required preconditions
- impact
- concrete remediation
- a test or check that would prove the remediation
Separate confirmed findings from defense-in-depth suggestions. If no finding survives inspection, state that clearly and list any unreviewed boundary that limits confidence.