gstack-cso
Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.
Informations de source
- Dépôt
- LING71671/Open-ClaudeCode
- Dernière activité de la source
- 8 juin 2026 à 18:43
- Langue détectée de SKILL.md
- anglais
- Étoiles
- 970
- Forks
- 1 216
Options d'installation
Le prompt qui vérifie d'abord la source est sélectionné par défaut. Vous pouvez passer à une commande directe ou télécharger une copie locale.
Vérifiez les fichiers source
Lisez SKILL.md et les fichiers associés affichés par SkillsMP avant de décider de l'installer.
Affichage de SKILL.md
SKILL.md
Instructions source · Aperçu en lecture seule- name
- gstack-cso
- description
- Security audit workflow for OPC code, providers, plugins, Electron surfaces, local HTTP bridges, filesystem access, and command execution.
- allowed-tools
- ["Read","Grep","Glob","Bash"]
# gstack-cso
Use this skill for a security review with OWASP and STRIDE lenses.
## Scope
Prioritize OPC-specific attack surfaces:
- Electron main/preload/renderer IPC
- Local provider bridges and localhost auth
- API key and token storage
- Plugin, hook, skill, and MCP loading
- Shell command construction and tool permissions
- File reads/writes, path traversal, symlinks, and workspace boundaries
- Prompt injection from web, files, tool output, or plugin content
## Workflow
1. Map the trust boundaries and data flows.
2. Identify assets: secrets, filesystem access, provider credentials, session state, command execution, and user prompts.
3. Review entrypoints that cross boundaries.
4. Test high-confidence concerns with direct code evidence.
5. Ignore speculative issues unless there is a concrete exploit path.
## Output
For each finding include:
- Severity
- Affected file or component
- Exploit scenario
- Evidence
- Recommended remediation
Also include a short "Not Findings" section for checked risks that are already mitigated.
Voir sur GitHub