Security review
Configuração global do Cursor: user rules, agent skills, slash commands e hooks com scripts de instalação.
npx -y skills add JoaoAlavarse/cursor-config --skill security-reviewAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 15 days oldThe repository was created 15 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.
- 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
Evaluates code, configuration and system design to identify security risks and recommend practical mitigations. Use when reviewing security, auth flows, input handling, or secrets management.
SKILL.md
3.2 KB, as published. Nobody here has run it
Objective
Evaluate the implementation to identify security risks, assess their severity and recommend practical mitigations.
Prioritize realistic threats based on the application's context rather than theoretical vulnerabilities.
Context
Before reviewing:
- If project rules are available, read and follow them.
- Otherwise, infer the project's conventions from the existing codebase.
- Respect the project's security architecture and documented security requirements.
- Evaluate security within the application's business, deployment and threat context.
- Do not assume every application requires the same level of security.
Review Process
- Understand the application's purpose and trust boundaries.
- Identify sensitive assets, data and operations.
- Review authentication, authorization and session management.
- Review input validation, output encoding and data handling.
- Review communication with external systems.
- Review secrets, credentials and configuration management.
- Identify realistic attack vectors supported by the available evidence.
- Assess exploitability, likelihood and impact of identified risks.
- Recommend mitigations proportional to the identified risks.
Review Guidelines
Base conclusions on observable evidence.
Clearly distinguish facts, assumptions and recommendations.
Avoid reporting theoretical vulnerabilities without evidence.
Evaluate realistic attack scenarios.
Consider both application and infrastructure security when relevant.
Evaluate whether security controls are appropriate for the application's risk profile.
Avoid recommending security measures whose complexity outweighs their practical benefit.
Consider the impact of recommendations on usability and maintainability.
Do not classify every issue as high severity.
When uncertainty exists, explain what additional evidence would be needed.
Evaluate whether existing security controls are appropriate rather than simply missing.
Prefer layered mitigations over relying on a single security control.
Avoid recommending security measures that significantly increase operational complexity unless justified by the associated risk.
Do not infer the existence of vulnerabilities solely from the absence of visible security controls.
Avoid false positives by distinguishing confirmed findings from potential concerns that require additional verification.
Output
Summary
Provide an overall assessment of the application's security posture.
Strengths
Identify effective security controls already present.
Findings
Describe each identified security finding.
For each finding include:
- Description
- Potential Impact
- Likelihood
- Severity (Low, Medium, High or Critical), based on exploitability and potential impact.
- Evidence
- Recommended Mitigation
Overall Risk
Summarize the application's overall security risk.
Priority
Prioritize the findings based on risk reduction and implementation effort.