sakura-security

Audit application trust boundaries and release exposure with evidence-backed security findings.

3|1|Updated Sep 9, 2026
One-click install
npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-security-v20227
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sakura-security
Source: https://github.com/v20227/using-sakura-dev/tree/main/skills/sakura-security
Command: npx skills add https://github.com/v20227/using-sakura-dev --skill sakura-security-v20227

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Security reviews often produce vague warnings, unverified scanner output, or one-size-fits-all checklists that ignore how an application actually works. This Skill performs scoped, read-only security audits that trace untrusted input to privileged effects and return concrete, evidence-backed findings instead of speculation. ## Core Features & Use Cases - Trust Boundary Analysis: Traces untrusted input across frontend, API, IPC, plugin, file, database, shell, and external-service boundaries, inspecting enforcement where effects actually happen. - Evidence-Backed Findings: Each finding includes location, entrypoint-to-effect path, required conditions, severity reasoning, verification performed, and the smallest useful repair, separating demonstrated failures from unverified hypotheses. - Sensitive Data and Dependency Review: Checks secrets in source, config, logs, and bundles with redacted output, and resolves dependency findings against actually installed versions and current advisories. - Use Case: Before publishing a desktop app, ask for a security audit. The Skill reviews IPC permissions, secret handling, and release exposure, then reports blockers versus non-blocking hardening without modifying any code. ## Quick Start Ask the assistant to audit this project for security risks across its trust boundaries and report evidence-backed findings without changing any code.

Frequently Asked Questions about sakura-security

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

FAQPage Schema
How do I audit my application for security vulnerabilities?▼

Request a security audit describing your application type and scope. The audit traces untrusted input to privileged effects across frontend, API, file, and database boundaries, then reports findings with concrete locations, impact reasoning, and minimal repairs.

What does a security audit of code actually check?▼

It verifies authentication and authorization enforcement, input and output handling, sensitive-data exposure in source and logs, session and cryptographic use, and dependency findings resolved against installed versions. Each finding distinguishes demonstrated failures from unverified hypotheses.

Does a security audit modify my code or project files?▼

No, a security audit is read-only unless you separately authorize repairs. Non-mutating local checks and isolated reproductions with synthetic data may run, but production probing, destructive payloads, and credential testing require explicit authorization.

Can dependency scanner results be trusted as real vulnerabilities?▼

Automated findings are leads to triage, not proof of reachability. Each finding is resolved against the actual installed or locked version, runtime exposure, and current primary advisories; failed or unavailable scans are reported as coverage gaps, not clean results.

What happens if leaked secrets are found in my repository?▼

The finding is reported with redacted output, never reproducing the secret value. Removing it from current files is not treated as revocation; remaining exposure in history and prior artifacts is reported, and containment actions require separate authorization.

When should I not run a full security audit?▼

Ordinary small edits do not justify a full audit. For bounded changes, only the affected trust boundaries and callers are reviewed, widening only when the change or a concrete finding justifies broader scope.