seis-security

Review SEIS repository changes for secrets, permissions, and release-blocking security risks.

1|Updated Jun 5, 2026
One-click install
npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-security-emirhankudun-ux
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seis-security
Source: https://github.com/emirhankudun-ux/SEIS/tree/main/plugins/seis-security/skills/seis-security
Command: npx skills add https://github.com/emirhankudun-ux/SEIS --skill seis-security-emirhankudun-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews in the SEIS ecosystem are easy to skip or perform inconsistently, leading to leaked secrets, over-privileged access, weak SSH/VPN configurations, and unverified release claims. This Skill provides a structured security review lane so every change touching secrets, cloud access, dependencies, or CI gates is checked against existing SEIS policies before release. ## Core Features & Use Cases - Threat and Secret Review: Inspect changes for secret leakage, dependency risk, permission scope, and data exposure without printing sensitive values. - Access Hardening Checks: Validate SSH/VPN hardening, cloud access policy separation, and plugin/connector permission boundaries using existing SEIS check scripts. - Release Readiness Gates: Run release-blocking checks such as npm run check:seis-god-mode-release-readiness and report status as pass, blocked, or unverified. - Use Case: Before merging a pull request that adds a new cloud deployment connector, use this Skill to verify least-privilege permissions, confirm no credentials are exposed, and run the cloud access policy and SSH hardening checks. ## Quick Start Use $seis-security to review this SEIS change for security, secrets, rollback, and release risk.

Frequently Asked Questions about seis-security

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run a security review on a SEIS repository change?▼

Start by checking git status and branch state, then identify the security surface such as secrets, dependencies, cloud targets, or CI gates. Read the nearest source of truth like SECURITY.md or docs/governance, then run the relevant SEIS check scripts before reporting status.

What security checks does SEIS run before a release?▼

SEIS provides npm check scripts including check:cloud-access-policy, check:ssh-hardening-contract, check:seis-ssh-access-model, and check:seis-god-mode-release-readiness. These validate access policies, SSH configuration, and overall release readiness as blocking gates.

How do I check for leaked secrets without exposing them?▼

Scan for the presence of API keys, tokens, private keys, certificates, and .env contents without printing their values. Report the file location and secret type only, and never weaken controls or expose credentials in logs or output.

Does an installed plugin mean a connector is authenticated?▼

No. Installed plugins or visible connector cards must not be treated as authenticated. Authentication status requires explicit verification, and public cloud access must be kept separate from team or workplace VPN cloud access models.

When should a security review block a SEIS release?▼

Block a release when check scripts fail, secrets are exposed, permissions exceed least privilege, or validation evidence is missing. Report status as blocked or unverified rather than claiming safe or ready without evidence, and record rollback steps.