---
name: Gstack Cso
slug: gstack-cso
category: Quality
description: Gstack Cso guides security reviews of OPC code using OWASP and STRIDE lenses. Use it to inspect Electron IPC, local bridges, secrets, plugins, command execution, and file access.
github: "https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-cso"
language: TypeScript
stars: 945
forks: 1224
install: "npx degit https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-cso ~/.claude/skills/gstack-cso"
installs_to: ~/.claude/skills/gstack-cso
source_path: plugins/gstack-workflows/skills/gstack-cso/SKILL.md
collection_size: 15
category_size: 1354
collection_url: "https://dirskills.com/collections/LING71671/Open-ClaudeCode"
added: 2026-08-21T05:15:31.228Z
last_synced: 2026-08-21T05:15:31.228Z
canonical_url: "https://dirskills.com/skills/gstack-cso"
---

# Gstack Cso

Gstack Cso guides security reviews of OPC code using OWASP and STRIDE lenses. Use it to inspect Electron IPC, local bridges, secrets, plugins, command execution, and file access.

**Install:**

```bash
npx degit https://github.com/LING71671/Open-ClaudeCode/tree/main/plugins/gstack-workflows/skills/gstack-cso ~/.claude/skills/gstack-cso
```

## README

# 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.