security

Reviews authentication, authorization, input validation, data protection, and dependency safety.

11|1|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/Arcanada-one/datarim --skill security-arcanada-one
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security
Source: https://github.com/Arcanada-one/datarim/tree/main/skills/security
Command: npx skills add https://github.com/Arcanada-one/datarim --skill security-arcanada-one

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Security work is often inconsistent and reactive, leading to avoidable vulnerabilities, unsafe handling of secrets, and incomplete incident response.

Core Features & Use Cases

  • Operational security guidelines covering authentication/authorization, input validation, and data protection so changes follow proven practices.
  • Dependency safety and audit-ready phrasing to help keep security checks consistent across ecosystems and avoid misleading or outdated instructions.
  • Incident and threat-model recipes for recon vs compromise, secure include/path threat modeling, safe git history scrubbing, and macOS Tailscale + VPN coexistence.

Quick Start

Use the security skill to perform a focused security review when you are about to change authentication logic, handle secrets/PII, or investigate a suspicious file-access incident.

Frequently Asked Questions about security

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

FAQPage Schema
How do I perform a security review for authentication and authorization logic changes?

Perform a security review by applying stack-neutral audit phrasing and prescribed verification gates across authentication, authorization, input validation, and data protection to ensure changes follow proven practices and avoid false positives.

What is the best way to safely scrub secrets from git history?

The best way to safely scrub secrets from git history is to follow prescribed incident and threat-model recipes that provide safe remediation steps, ensuring sensitive data is completely removed without corrupting repository integrity or leaving misleading audit trails.

How do I conduct a dependency audit without causing false positives?

Conduct a dependency audit using audit-ready phrasing and prescribed verification gates to keep security checks consistent across ecosystems, avoiding misleading or outdated instructions that can trigger false positives or incomplete remediation during dependency safety checks.

When do I need to update threat models for include path vulnerabilities?

You need to update threat models for include path vulnerabilities when performing secure include and path threat modeling, using specific incident and threat-model recipes to accurately map recon versus compromise scenarios and apply safe remediation steps.

Does this security review approach work across different tech stacks?

Yes, this security review approach works across different tech stacks by using stack-neutral audit phrasing, ensuring dependency safety and operational security guidelines remain consistent across ecosystems without relying on misleading or outdated framework-specific instructions.