security-sentinel

Scan workspaces for vulnerabilities, exposed secrets, and misconfigurations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/nakamotosai/chii --skill security-sentinel-nakamotosai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-sentinel
Source: https://github.com/nakamotosai/chii/tree/main/skills/security-sentinel
Command: npx skills add https://github.com/nakamotosai/chii --skill security-sentinel-nakamotosai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Security Sentinel scans the workspace for security vulnerabilities, exposed secrets, and misconfigurations to prevent data leaks and insecure configurations.

Core Features & Use Cases

  • Scans for exposed API keys in text files.
  • Checks file permissions (basic).
  • Reports findings to stdout.

Quick Start

Run node skills/security-sentinel/scan.js to perform a security assessment of the workspace.

Frequently Asked Questions about security-sentinel

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

FAQPage Schema
How do I scan my Node.js workspace for exposed secrets and API keys?

To scan a Node.js workspace for exposed secrets, run the execution script to perform automated pattern-based secret detection across text files and report findings to stdout.

What is automated workspace security scanning and how does it detect vulnerabilities?

Automated workspace security scanning detects vulnerabilities, exposed secrets, and misconfigurations by applying pattern-based checks to codebases, configurations, and deployment environments.

Can I audit file permissions and misconfigurations in my codebase automatically?

Yes, you can audit file permissions and misconfigurations automatically by running the Node.js scanning script, which performs basic permission checks and reports risks to stdout.

Does this workspace security audit require any external dependencies to run?

No, this workspace security audit requires zero external dependencies, operating entirely through a standalone Node.js execution script to detect vulnerabilities and secrets.

What is the best way to check for insecure configurations before deployment?

The best way to check for insecure configurations before deployment is to run an automated workspace scanner that evaluates codebases and deployment environments for misconfigurations and exposed secrets.

What are the limitations of pattern-based secret detection in a Node.js workspace scanner?

The limitations of pattern-based secret detection include basic file permission checks and stdout reporting only, meaning it identifies specific secret patterns rather than performing deep contextual data flow analysis.