security-quick-review
Review Code Changes for Security Risks
Code changes can introduce security problems that routine reviews miss. This skill guides focused AI triage with evidence, realistic severity, and concrete fixes.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "security-quick-review" from https://skillstore.io/skills/agentkitco-security-quick-review.md and its manifest at https://skillstore.io/api/skills/agentkitco-security-quick-review/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "security-quick-review". Illustrative scenario: an endpoint accepts a record identifier but never verifies that the caller owns the record.
Resultado esperado:
- Scope: the changed endpoint and its authorization checks; deployment behavior was not reviewed.
- HIGH: Missing ownership validation could let an authenticated caller access another user's record by changing the identifier.
- Fix: enforce record-level authorization on the server before returning data.
- A real finding must include the affected file and line; this illustration has no source attachment.
- Limits: automated triage, not a security audit.
Usando "security-quick-review". Illustrative scenario: a credential was removed from the current change but remains visible in repository history.
Resultado esperado:
- Scope: the selected change and its repository history.
- HIGH: A historical credential remains exposed even after removal from current code.
- Fix: rotate or revoke the credential and investigate its use; deleting current text does not invalidate it.
- Evidence should identify the source location without reproducing the secret value.
- Could not verify: whether the credential remains active.
Auditoría de seguridad
SeguroAll five static findings are false positives from Markdown formatting, defensive terminology, and scoped code inspection. The only suggested commands inspect Git changes and history; the skill forbids live exploitation and repeating secret values. No evidence found of malicious instructions, credential exfiltration, or unsafe execution directives.
Factores de riesgo
⚙️ Comandos externos (3)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/agentkitco-security-quick-review/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/agentkitco-security-quick-review?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/agentkitco-security-quick-review?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/agentkitco-security-quick-review/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/agentkitco-security-quick-review.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
agentkitco. (2026). security-quick-review security audit report (audit version 2) [Author version 1.0]. Skillstore. https://skillstore.io/skills/agentkitco-security-quick-review/audits/2Cita BibTeX
@techreport{agentkitco-agentkitco-security-quick-review-2026,
author = {agentkitco},
title = {security-quick-review security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/agentkitco-security-quick-review/audits/2},
note = {Author version 1.0}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "security-quick-review security audit report (audit version 2)"
version: "1.0"
type: report
authors:
- name: "agentkitco"
date-released: "2026-10-22"
url: "https://skillstore.io/skills/agentkitco-security-quick-review/audits/2"
identifiers:
- type: other
value: "skillstore:agentkitco-security-quick-review:audit:2"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Check a Pull Request Before Merge
Review changed input handlers and related code for injection, exposed secrets, and unsafe error behavior.
Review Access Controls
Examine routes and actions for missing server-side checks and access to another user's records.
Inspect Dependency and Configuration Changes
Review package additions, lockfiles, debug settings, and new CI or cloud permissions within the selected change.
Prueba estos prompts
Review my current diff for likely security issues. State the scope, cite evidence, suggest fixes, and list anything you cannot verify.
Review [endpoint] and its called code for untrusted input, injection, authentication, authorization, and data exposure. Report evidence and concrete fixes without live exploitation.
Review [directory] and its scoped Git changes and history for exposed secrets, dependency risks, and configuration weaknesses. Never reproduce secret values; recommend rotation when needed.
Review [workflow] across changed code and called modules. Trace authorization, input boundaries, unsafe operations, and failure behavior. Separate evidence from uncertainty and identify human-review needs.
Mejores prácticas
- Specify the diff, directory, endpoint, or workflow and include relevant called code.
- Require file and line evidence, realistic impact, concrete fixes, and explicit verification gaps.
- Rotate exposed secrets and obtain human review for workflows handling money, health, or identity data.
Evitar
- Treating a clean triage report as proof that an application is secure.
- Pasting secret values into reports or assuming deletion removes historical exposure.
- Attempting live exploitation or accepting generic vulnerability lists without source evidence.
Preguntas frecuentes
Is this a complete security audit?
Which AI tools are supported?
What does the review cover?
Does it run attacks against live systems?
How does it handle exposed secrets?
What should a useful report include?
Detalles del desarrollador
Autor
agentkitcoLicencia
MIT
Versión del autor
v1.0
Revisión de Skillstore
r2
Aviso de versión
La versión declarada por el autor no es un SemVer válido.
Ref.
18efac79a818d7e997295839638fdd21906cfd1c
Actualidad del mantenimiento
22/10/2026
Uso
6 descargas · 0 vistas
Estructura de archivos
📄 SKILL.md