rune-sentinel

Blocks unsafe code before commit via secret scanning, OWASP checks, and dependency audits.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/dangvu008/VietTruyen --skill rune-sentinel-dangvu008
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: rune-sentinel
Source: https://github.com/dangvu008/VietTruyen/tree/main/.agents/skills/rune-sentinel
Command: npx skills add https://github.com/dangvu008/VietTruyen --skill rune-sentinel-dangvu008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? It prevents secrets, injection vulnerabilities, vulnerable dependencies, and destructive commands from reaching your repository by acting as a hard security gate before every commit or deployment. ## Core Features & Use Cases - Secret & Credential Scanning: Detects hardcoded API keys, tokens, private keys, and high-entropy strings using core and extended Gitleaks-style regex patterns, including git history scans. - OWASP & Framework Checks: Flags SQL injection, XSS, CSRF, missing input validation, plus framework-specific risks for Django, React/Next.js, Express, Electron, and Tauri. - Dependency & Supply Chain Audit: Runs npm audit, pip-audit, or cargo audit and assesses new dependencies for typosquatting, unmaintained packages, and unpatched CVEs. - Use Case: Before committing an authentication feature, run the scan to catch a hardcoded JWT secret, an unparameterized SQL query, and a critical CVE in a newly added package — all reported as BLOCK findings that halt the commit until fixed. ## Quick Start Ask the agent to run a sentinel security scan on all staged changes before committing and report any BLOCK or WARN findings.

Frequently Asked Questions about rune-sentinel

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

FAQPage Schema
How do I scan code for hardcoded secrets before committing?▼

Run the sentinel scan on staged files to detect patterns like AWS keys, GitHub tokens, private keys, and high-entropy strings. Any match produces a BLOCK finding that halts the commit until the secret is removed.

What security checks does a pre-commit security gate perform?▼

It performs secret scanning, dependency audits via npm audit or pip-audit, OWASP checks for SQL injection, XSS, and CSRF, destructive command detection, and framework-specific checks for Django, React, Express, Electron, and Tauri.

Does the dependency audit work if npm audit is not installed?▼

If the audit tool is missing, the scan logs an INFO finding stating the tool was not found and skips the dependency check. It never blocks a commit due to missing tooling.

Why did the security scan flag my test fixtures as secrets?▼

Test fixtures with hardcoded values are a known false-positive source. The six-gate validation and safe-exception rules downgrade findings in test, fixtures, and __mocks__ directories, and .example files are excluded.

Can the scan enforce custom project or organization security policies?▼

Yes. If .rune/contract.md or .rune/org/org.md exists, staged changes are validated against project contract rules and organization policies such as reviewer requirements and compliance frameworks. Contract violations are hard BLOCK gates.